Triple
T12730516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Washington State Route 167 |
E304223
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 167 |
E567291
|
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 167 | Statement: [Washington State Route 167, abbreviation, SR 167]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 167 Context triple: [Washington State Route 167, abbreviation, SR 167]
-
A.
SR 167
chosen
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
B.
SR 165
SR 165 is a state highway in Maine that serves as a regional connector route between several communities in the northern part of the state.
-
C.
SR 162
SR 162 is a state highway in Tennessee that serves as a key connector route in the Knoxville metropolitan area.
-
D.
SR 117
SR 117 is a state highway in Maine that runs through several counties, connecting multiple rural towns and regional routes.
-
E.
SR 116
SR 116 is a state highway in Tennessee that serves as a regional connector route through rural communities.
- 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_69d7bdf1426c8190a4402e1c4cdec33a |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d96467a2248190aff1ebb5db84b3c6 |
completed | April 10, 2026, 8:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f69b8c84308190b57d3b5b04bb4a78 |
completed | May 3, 2026, 12:49 a.m. |
Created at: April 9, 2026, 5:25 p.m.