Triple

T19972402
Position Surface form Disambiguated ID Type / Status
Subject Mexican railroads E480110 entity
Predicate dominantTraction P132066 FINISHED
Object diesel locomotives 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: diesel locomotives | Statement: [Mexican railroads, dominantTraction, diesel locomotives]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: dominantTraction
Context triple: [Mexican railroads, dominantTraction, diesel locomotives]
  • A. primaryTraction
    Indicates that one entity serves as the main source or means of traction, pulling power, or driving force for another entity or process.
  • B. typicalTractionType chosen
    Indicates the usual or most common type of traction mechanism associated with an entity (such as how it is typically powered or driven).
  • C. usedTractionType
    Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
  • D. secondaryTraction
    Indicates a supporting or additional influence, pull, or driving force that complements a primary source of traction or momentum in a relationship or process.
  • E. dominantOn
    Indicates that one entity exerts control, authority, or prevailing influence over another in a given context.
  • 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_69d8e523c19881909f9197037200dde6 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e65bca94c0819095c902a411c4c4b8 completed April 20, 2026, 5 p.m.
PD Predicate disambiguation batch_69e537fae79c81909eae39500766d0b6 completed April 19, 2026, 8:15 p.m.
Created at: April 10, 2026, 1:54 p.m.