Triple

T21120625
Position Surface form Disambiguated ID Type / Status
Subject Interstate 820 E520419 entity
Predicate hasAlternateName P39 FINISHED
Object Loop 820 NE NERFINISHED

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: Loop 820 | Statement: [Interstate 820, hasAlternateName, Loop 820]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Loop 820
Context triple: [Interstate 820, hasAlternateName, Loop 820]
  • A. Loop 820 chosen
    Loop 820 is a major beltway highway encircling much of the Fort Worth, Texas metropolitan area, serving as a key route for regional traffic and suburban access.
  • B. Loop 286
    Loop 286 is a state highway loop that serves as a beltway around the city of Paris in Lamar County, Texas.
  • C. Loop 1604
    Loop 1604 is a major highway encircling much of San Antonio, Texas, serving as a key route for regional traffic and access to suburban districts and commercial areas.
  • D. Loop 610
    Loop 610 is a major freeway loop encircling central Houston, Texas, serving as a key transportation corridor that connects numerous neighborhoods and business districts, including Uptown.
  • E. Loop 323
    Loop 323 is a primary circumferential highway that serves as the main loop route around the city of Tyler, Texas.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e0b50a623881909c0bbaf4f2c055e7 completed April 16, 2026, 10:08 a.m.
NER Named-entity recognition batch_69e72233a43481909535560514d388be completed April 21, 2026, 7:07 a.m.
Created at: April 16, 2026, 2:55 p.m.