Triple

T21768299
Position Surface form Disambiguated ID Type / Status
Subject BNSF La Junta Subdivision E537353 entity
Predicate hasMaximumSpeedCategory P72264 FINISHED
Object Class 4 track (typical freight) 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: Class 4 track (typical freight) | Statement: [BNSF La Junta Subdivision, hasMaximumSpeedCategory, Class 4 track (typical freight)]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasMaximumSpeedCategory
Context triple: [BNSF La Junta Subdivision, hasMaximumSpeedCategory, Class 4 track (typical freight)]
  • A. hasSpeedLimitCategory chosen
    Indicates that an entity is associated with a specific category or classification of speed limit.
  • B. maxSpeed
    Indicates the greatest possible speed at which an entity can move or operate under specified conditions.
  • C. hasTopSpeedSection
    Indicates that an entity includes or is associated with a segment or portion where the maximum or top speed is defined, reached, or relevant.
  • D. designedSpeedKmH
    Indicates the maximum speed in kilometers per hour that something is intended or engineered to achieve under its design specifications.
  • E. category1UpperBound_mph
    Indicates the maximum speed limit, in miles per hour, that defines the upper boundary of category 1.
  • 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_69e0c46f5d1c8190bf830409e98464e5 completed April 16, 2026, 11:13 a.m.
NER Named-entity recognition batch_69f031ab57808190b9af6d8f0ead1051 completed April 28, 2026, 4:03 a.m.
PD Predicate disambiguation batch_69e6be6299988190a34c98fa76d94700 completed April 21, 2026, 12:01 a.m.
Created at: April 16, 2026, 6:51 p.m.