Triple

T36158928
Position Surface form Disambiguated ID Type / Status
Subject 4-8-2 Mountain steam locomotives E1045817 entity
Predicate hasLeadingTruck P196677 FINISHED
Object two-axle leading truck 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: two-axle leading truck | Statement: [4-8-2 Mountain steam locomotives, hasLeadingTruck, two-axle leading truck]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLeadingTruck
Context triple: [4-8-2 Mountain steam locomotives, hasLeadingTruck, two-axle leading truck]
  • A. hasSeparateLeadingTruck
    Indicates that an object or vehicle is accompanied by a distinct, independently operated leading truck unit.
  • B. hasSeparateTrailingTruck
    Indicates that an entity is accompanied by a distinct, independently attached trailing truck or carriage rather than having it integrated into its main structure.
  • C. hasTrailingTruckType
    Indicates that an entity is associated with a specific type of truck positioned at the rear or trailing end.
  • D. hasTrailerCar
    Indicates that one vehicle is connected to and pulling another vehicle configured as a trailer car.
  • E. hasTruckTraffic
    Indicates that there is truck-related vehicular movement or flow occurring on or through a specified location or route.
  • F. None of above. chosen

Provenance (4 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_69f76e38903c8190a52887620f90aabe completed May 3, 2026, 3:48 p.m.
NER Named-entity recognition batch_69fe610e1f6881908f10070ba64643cf completed May 8, 2026, 10:17 p.m.
PD Predicate disambiguation batch_69fe604c6c008190ad659e9b9fa82f7b completed May 8, 2026, 10:14 p.m.
PDg Predicate description generation batch_69fe610d75a48190bfd08a9bb957fcd3 completed May 8, 2026, 10:17 p.m.
Created at: May 3, 2026, 4:08 p.m.