Triple

T5096083
Position Surface form Disambiguated ID Type / Status
Subject Heritage Corridor line E114866 entity
Predicate usesSharedFreightTracks P61077 FINISHED
Object yes 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: yes | Statement: [Heritage Corridor line, usesSharedFreightTracks, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesSharedFreightTracks
Context triple: [Heritage Corridor line, usesSharedFreightTracks, yes]
  • A. isOnFreightRoute
    Indicates that something lies along or is included within a designated freight transportation route used for moving goods.
  • B. hasExpressTracks
    Indicates that a transportation route or facility includes tracks designated for express service, allowing faster travel with fewer stops than regular tracks.
  • C. sharesTrunkWith
    Indicates that two entities have a common trunk or main stem from which they both extend or branch.
  • D. usesRollingStockCompatibleWith
    Indicates that one entity operates using rolling stock that is technically and operationally compatible with the rolling stock standards or systems associated with another entity.
  • E. usesRollingStock
    Indicates that one entity employs or operates specific rolling stock (such as rail vehicles) in its activities or services.
  • 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_69bd443fc49c819089629c00e311310c completed March 20, 2026, 12:57 p.m.
NER Named-entity recognition batch_69bd75652a8081908386718f1fdb1de3 completed March 20, 2026, 4:27 p.m.
PD Predicate disambiguation batch_69bd715e06808190931934dc9930f997 completed March 20, 2026, 4:10 p.m.
PDg Predicate description generation batch_69bd738ac2e0819099c06cdcc5e21d28 completed March 20, 2026, 4:19 p.m.
Created at: March 20, 2026, 1:40 p.m.