MétaCan
Menu
Back to cohort
Record W2337843166 · doi:10.12735/jbm.v4i4p01

Buyers’ Perspective of Buyer-Supplier Relationship Development: Interaction of Key Variables

2015· article· en· W2337843166 on OpenAlex
Faiza Khoja, Jeffery Adams, Ralph G. Kauffman

Why this work is in the frame

A frame that forgets how it found something cannot be audited. These are the routes that admitted this work.

venuePublished in a venue whose home country is Canada.
no affNo Canadian affiliation: this work is invisible to an affiliation-only frame.
No Canadian affiliation. An affiliation-only frame, the usual design, would never have seen this work. It is one of the works that make the case for inverting the frame.

Bibliographic record

VenueJournal of Business & Management · 2015
Typearticle
Languageen
FieldBusiness, Management and Accounting
TopicOutsourcing and Supply Chain Management
Canadian institutionsnot available
Fundersnot available
KeywordsPerspective (graphical)Key (lock)BusinessSupplier relationship managementProcess managementIndustrial organizationMarketingComputer scienceSupply chainSupply chain managementComputer securityArtificial intelligence

Abstract

fetched live from OpenAlex

In this paper, we propose and test a three-stage model. A relationship begins at the Pre-Deal Stage (t-1), where, Buyer and Supplier Power are likely to impact Input Commitment. The relationship moves on to the Deal Enactment Stage (t), where the Input Commitment is likely to foster Low Relational Embeddedness. This, in turn, develops Contractual Trust that leads to a business deal and Attitudinal Commitment. Depending on requirements and mutual satisfaction, the relationship may then move to the Continuation Stage (t+1), where the developed Attitudinal Commitment enhances High Relational Embeddedness. From this comes Competence-based Trust and Temporal Commitment. Temporal Commitment and High Relational Embeddedness is likely to further produce Goodwill Trust and improved Overall Performance. This research study extends existing literature by empirically testing a cohesive model, which explains the different, multidimensional roles relational constructs can play in a relationship, and how these relationships evolve over time.

Fetched live from OpenAlex and de-inverted. Abstracts are not stored in this database: the inverted indexes are 8.6 GB of the frame’s 9.3 GB of text, and the host has 13 GB free.

Full frame distilled prediction

Teacher imitation

Not calibrated prevalence, not ground truth. Human validation pending. Learned from the 10,348 direct Codex labels and 10,348 direct Gemma labels. Candidate is the union of thresholded teacher heads; consensus is their intersection. These outputs are machine_predicted_unvalidated and are not human labels or direct frontier model labels.

metaresearch head score (Codex)0.002
metaresearch head score (Gemma)0.000
Version: codex-gemma-dda1882f352aValidation status: machine_predicted_unvalidated
Candidate categoriesnone
Consensus categoriesnone
DomainCandidate signal: none · Consensus signal: none
Study designCandidate signal: Not applicable · Consensus signal: none
GenreCandidate signal: Empirical · Consensus signal: Empirical
Teacher disagreement score0.495
Threshold uncertainty score0.917

Codex and Gemma teacher scores by category

CategoryCodexGemma
Metaresearch0.0020.000
Meta-epidemiology (narrow)0.0000.000
Meta-epidemiology (broad)0.0010.000
Bibliometrics0.0010.001
Science and technology studies0.0000.000
Scholarly communication0.0000.001
Open science0.0000.000
Research integrity0.0000.000
Insufficient payload (model declined to judge)0.0000.000

Machine scores (provisional)

The two teacher heads of the student model, read on this work. A score orders the frame for review; it never asserts a category, and the validation status ships verbatim with every row.

Baseline scores from an immature model (maturity gate not passed, 7 training rounds). Scores rank; they never assert a category.

Opus teacher head0.034
GPT teacher head0.246
Teacher spread0.212 · how far apart the two teachers sit on this one work
Validation statusscore_only:v0-immature-baseline · verbatim from the scoring run: score_only means the number may rank works, and no category label ships from it