Triple

T6402624
Position Surface form Disambiguated ID Type / Status
Subject Amtrak Empire Builder E144098 entity
Predicate endToEndTravelTime P46906 FINISHED
Object approximately 46 hours 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: approximately 46 hours | Statement: [Amtrak Empire Builder, endToEndTravelTime, approximately 46 hours]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: endToEndTravelTime
Context triple: [Amtrak Empire Builder, endToEndTravelTime, approximately 46 hours]
  • A. travelTimeTypical chosen
    Indicates the usual or expected amount of time it takes to travel between two locations under normal conditions.
  • B. travelTimeCategory
    Indicates the qualitative classification of how long a given travel or trip duration is (e.g., short, medium, long).
  • C. previousTravelTimeOnRoute
    Indicates the duration of travel that occurred earlier on the same route before the current segment or time period.
  • D. approximateDrivingTimeFromLAnse
    Indicates the estimated amount of time it takes to drive from L'Anse to another specified location.
  • E. hasApproximateWalkingTimeTo
    Indicates that there is an estimated or approximate amount of time it takes to walk from one entity to another.
  • 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_69c008dc56fc81908d43ffcc11d73bdd completed March 22, 2026, 3:21 p.m.
NER Named-entity recognition batch_69c068ade8c881908a0472f1de6b7c21 completed March 22, 2026, 10:09 p.m.
PD Predicate disambiguation batch_69c060f40ecc8190b1df17b96767675c completed March 22, 2026, 9:36 p.m.
Created at: March 22, 2026, 4:35 p.m.