Triple

T9250126
Position Surface form Disambiguated ID Type / Status
Subject GTE North E222299 entity
Predicate longDistanceProvision P42175 FINISHED
Object intraLATA long-distance service 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: intraLATA long-distance service | Statement: [GTE North, longDistanceProvision, intraLATA long-distance service]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: longDistanceProvision
Context triple: [GTE North, longDistanceProvision, intraLATA long-distance service]
  • A. longDistanceService chosen
    Indicates that a service operates over large geographic distances, typically connecting locations that are far apart rather than nearby.
  • B. longDistanceOperator
    Indicates that an entity performs telephone or communication services that connect calls over long distances between different geographic areas.
  • C. platformsForLongDistanceServices
    Indicates that something serves as a designated platform or set of platforms used for operating or providing long-distance services.
  • D. hasLongDistancePathAccess
    Indicates that an entity has the ability or right to use a path or route that spans a long distance.
  • E. longDistanceTrail
    Indicates that a trail or route spans a considerable distance, typically intended for extended or multi-day travel.
  • 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_69ca841d2b18819089f9faf5b2c2aec0 completed March 30, 2026, 2:09 p.m.
NER Named-entity recognition batch_69cd05f7e9848190939f9199d0c1a572 completed April 1, 2026, 11:48 a.m.
PD Predicate disambiguation batch_69cc7a4e79e48190b3200247f4624867 completed April 1, 2026, 1:52 a.m.
Created at: March 30, 2026, 7:31 p.m.