Triple

T11184951
Position Surface form Disambiguated ID Type / Status
Subject Georgia State Route 16 E264639 entity
Predicate abbreviation P43 FINISHED
Object SR 16 E264638 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: SR 16 | Statement: [Georgia State Route 16, abbreviation, SR 16]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: SR 16
Context triple: [Georgia State Route 16, abbreviation, SR 16]
  • A. SR 16
    SR 16 is a state highway in Maine that runs east–west across the central and western parts of the state, connecting several rural communities and major routes.
  • B. SR 16 chosen
    SR 16 is a state highway in Georgia that runs east–west across the central part of the state, connecting several towns and major routes.
  • C. SR 160
    SR 160 is a Nevada state highway that connects Las Vegas to Pahrump and serves as a major route through the Spring Mountains region.
  • D. SR 167
    SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
  • E. SR 168
    SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
  • 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_69d6aa9dafac8190bd90d2c74f661aa7 completed April 8, 2026, 7:21 p.m.
NER Named-entity recognition batch_69d7e8abbeac8190ad6e419258999f4e completed April 9, 2026, 5:58 p.m.
NED1 Entity disambiguation (via context triple) batch_69e483d0f4548190b97c7725a9f7c0e6 completed April 19, 2026, 7:27 a.m.
Created at: April 8, 2026, 9:29 p.m.