Triple

T5481931
Position Surface form Disambiguated ID Type / Status
Subject Northeast Corridor electrified services E123485 entity
Predicate usesTraction P39844 FINISHED
Object electric 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: electric locomotives | Statement: [Northeast Corridor electrified services, usesTraction, electric locomotives]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesTraction
Context triple: [Northeast Corridor electrified services, usesTraction, electric locomotives]
  • A. usedTractionType chosen
    Indicates the type of traction or drive mechanism that was employed in performing the action or operating the entity.
  • B. currentTractionType
    Indicates the type or mode of traction currently being applied or in use in a given context.
  • C. usesTrackage
    Indicates that one transportation operator or service runs its vehicles over railway or transit tracks that are owned or controlled by another entity.
  • D. primaryTraction
    Indicates that one entity serves as the main source or means of traction, pulling power, or driving force for another entity or process.
  • E. successorTractionType
    Indicates that one traction type directly follows or replaces another in a sequence or evolution of traction systems.
  • 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_69bd4648883481909e9775d43300c5fa completed March 20, 2026, 1:06 p.m.
NER Named-entity recognition batch_69bd93e5d0f08190a6cc9fc408b7c5bb completed March 20, 2026, 6:37 p.m.
PD Predicate disambiguation batch_69bd91a73b148190a865243536a4fe76 completed March 20, 2026, 6:27 p.m.
Created at: March 20, 2026, 2:09 p.m.