Triple
T6056606
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 167 |
E134927
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
|
E567291
|
NE FINISHED |
How this triple was built (4 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 167 | Statement: [State Route 167, abbreviation, SR 167]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 167 Context triple: [State Route 167, abbreviation, SR 167]
-
A.
SR 116
SR 116 is a state highway in Georgia that serves as an east–west transportation route connecting several communities in the west-central part of the state.
-
B.
SR 16
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 168
SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
-
D.
SR 188
SR 188 is a short California state highway that connects the city of Tecate to the U.S.–Mexico border in San Diego County.
-
E.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SR 167 Triple: [State Route 167, abbreviation, SR 167]
Generated description
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 167 Target entity description: SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
A.
SR 116
SR 116 is a state highway in Georgia that serves as an east–west transportation route connecting several communities in the west-central part of the state.
-
B.
SR 16
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 168
SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
-
D.
SR 188
SR 188 is a short California state highway that connects the city of Tecate to the U.S.–Mexico border in San Diego County.
-
E.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
- F. None of above. chosen
Provenance (5 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_69c00877b6d4819096b0e163728b73a3 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c0570bf01c8190a8b2c25b7805d403 |
completed | March 22, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c11d0e06288190b4389b43825d5929 |
completed | March 23, 2026, 10:59 a.m. |
| NEDg | Description generation | batch_69c11ec11864819084c31d98133ca53a |
completed | March 23, 2026, 11:06 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c11f29842881909acf88a1fa896354 |
completed | March 23, 2026, 11:08 a.m. |
Created at: March 22, 2026, 4:09 p.m.