Triple

T26377829
Position Surface form Disambiguated ID Type / Status
Subject OEM E660946 entity
Predicate usesComponentsFrom P9772 FINISHED
Object tier‑1 suppliers LITERAL FINISHED

How this triple was built (2 steps)

Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: tier‑1 suppliers | Statement: [OEM, usesComponentsFrom, tier‑1 suppliers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesComponentsFrom
Context triple: [OEM, usesComponentsFrom, tier‑1 suppliers]
  • A. componentFrom
    Indicates that one entity is derived from, produced by, or originates as a component of another entity.
  • B. usedComponent chosen
    Indicates that one entity has employed or incorporated another entity as a component in its structure, function, or operation.
  • C. otherComponentOf
    Indicates that one entity is a different part or member of the same larger whole or system as another entity.
  • D. usesConstituentsFrom
    Indicates that one entity is composed of, incorporates, or is derived from specific constituent parts provided by another entity.
  • E. isCoreComponentOf
    Indicates that something is an essential, foundational part required for the structure, function, or identity of another entity.
  • F. None of above.

Provenance (3 batches)

The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.

Step Stage Batch ID Status When
creating Elicitation batch_69ee812a698881908d6a58265995fa39 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f66c5c13808190887180099745673b completed May 2, 2026, 9:27 p.m.
PD Predicate disambiguation batch_69f66abddc448190a488852f8abdeb2c completed May 2, 2026, 9:21 p.m.
Created at: April 26, 2026, 11:02 p.m.