Triple

T12763778
Position Surface form Disambiguated ID Type / Status
Subject Gilbert Trail (Iowa) E305064 entity
Predicate usesFormerInfrastructure P6820 FINISHED
Object former railroad corridor 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: former railroad corridor | Statement: [Gilbert Trail (Iowa), usesFormerInfrastructure, former railroad corridor]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesFormerInfrastructure
Context triple: [Gilbert Trail (Iowa), usesFormerInfrastructure, former railroad corridor]
  • A. formerInfrastructure
    Indicates that an entity once served as infrastructure for another entity or system but no longer holds that functional status.
  • B. usesInfrastructure chosen
    Indicates that one entity makes use of, depends on, or operates through the infrastructure provided or managed by another entity.
  • C. formerlyUsedBy
    Indicates that an entity was used by another entity in the past but is no longer in use by that entity.
  • D. hasInfrastructureAbove
    Indicates that one entity’s infrastructure is physically located above or over another entity.
  • E. preservesInfrastructureOf
    Indicates that one entity maintains, protects, or sustains the functionality and integrity of another entity’s infrastructure.
  • 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_69d7bdf1fcd081909ffb0e0d6fa3a07d completed April 9, 2026, 2:55 p.m.
NER Named-entity recognition batch_69d96d8f9f588190bffdea878856204b completed April 10, 2026, 9:37 p.m.
PD Predicate disambiguation batch_69d96409739881909174ba005a986cb5 completed April 10, 2026, 8:56 p.m.
Created at: April 9, 2026, 5:28 p.m.