Triple

T37115052
Position Surface form Disambiguated ID Type / Status
Subject Dedicated Freight Corridor network (planned and existing links) E919094 entity
Predicate hasPlannedComponent P134005 FINISHED
Object East–West Dedicated Freight Corridor NE NERFINISHED

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: East–West Dedicated Freight Corridor | Statement: [Dedicated Freight Corridor network (planned and existing links), hasPlannedComponent, East–West Dedicated Freight Corridor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPlannedComponent
Context triple: [Dedicated Freight Corridor network (planned and existing links), hasPlannedComponent, East–West Dedicated Freight Corridor]
  • A. hasPlannedPart chosen
    Indicates that one entity includes another entity as a component or segment within a planned or scheduled whole.
  • B. plannedComponent
    Indicates that one entity is intended or scheduled to serve as a component or part of another entity in a planned or future configuration.
  • C. hasPlanningType
    Indicates that an entity is associated with a specific category or type used for planning or scheduling purposes.
  • D. hasPlannedLine
    Indicates that an entity is associated with a specific planned route or line intended for future or scheduled use.
  • E. hasPlanningStatus
    Indicates that an entity is associated with a particular stage, condition, or outcome in a planning or approval process.
  • 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_69f76e9c57148190ba789dd059645bb9 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fe38be079c8190a240191ac0e73e3a completed May 8, 2026, 7:25 p.m.
PD Predicate disambiguation batch_69fe350344508190930de2218156ca02 completed May 8, 2026, 7:09 p.m.
Created at: May 3, 2026, 4:15 p.m.