Triple

T8216998
Position Surface form Disambiguated ID Type / Status
Subject AL 21 E191957 entity
Predicate connectsTo P845 FINISHED
Object I-85 E61864 NE 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: I-85 | Statement: [AL 21, connectsTo, I-85]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: I-85
Context triple: [AL 21, connectsTo, I-85]
  • A. Interstate 85 chosen
    Interstate 85 is a major Interstate Highway in the southeastern United States that runs from Alabama to Virginia, serving key cities such as Atlanta, Charlotte, and Durham.
  • B. Interstate 540
    Interstate 540 is a beltway highway serving the Raleigh metropolitan area in North Carolina, facilitating regional traffic flow and suburban connectivity.
  • C. Interstate 140
    Interstate 140 is a short auxiliary Interstate highway serving the Knoxville, Tennessee area, providing a connector route around the city.
  • D. Interstate 20
    Interstate 20 is a major east–west U.S. highway running from Texas to South Carolina, serving as a key transportation corridor across the southern United States.
  • E. Interstate 82
    Interstate 82 is a major U.S. highway in the Pacific Northwest that connects central Washington to northeastern Oregon, facilitating regional travel and commerce.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69ca82c8c054819087fedd9a5436b8a3 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb776f41108190bed1c6a8ddbea374 completed March 31, 2026, 7:27 a.m.
NED1 Entity disambiguation (via context triple) batch_69cfdb70fbf881909daefb3162ba803c completed April 3, 2026, 3:23 p.m.
Created at: March 30, 2026, 5:44 p.m.