Triple
T18159718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 192 |
E434724
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 192 |
—
|
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: SR 192 | Statement: [State Route 192, abbreviation, SR 192]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 192 Context triple: [State Route 192, abbreviation, SR 192]
-
A.
SR 192
chosen
SR 192 is a state highway in Maine that connects rural communities in Washington County to larger regional routes.
-
B.
SR 191
SR 191 is a state highway in Maine that runs through Washington County, connecting coastal and inland communities.
-
C.
SR 190
SR 190 is a California state highway that runs east–west through the southern Sierra Nevada and Death Valley, connecting the Central Valley to the Nevada state line.
-
D.
SR 190
SR 190 is a state highway in Maine that serves as a short connector route, including access to the town of Eastport.
-
E.
SR 196
SR 196 is a state highway in Maine that connects the cities of Lewiston and Brunswick, serving as a key regional route in the state's road network.
- 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_69d8b90b7a188190b3fc7b8d4a6cd20a |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dec0e0388190af11ac167411da96 |
completed | April 19, 2026, 1:55 p.m. |
Created at: April 10, 2026, 10:30 a.m.