Triple
T22523769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virginia State Route 236 |
E556844
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 236 |
—
|
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 236 | Statement: [Virginia State Route 236, abbreviation, SR 236]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 236 Context triple: [Virginia State Route 236, abbreviation, SR 236]
-
A.
SR 236
chosen
SR 236 is a primary state highway in Northern Virginia commonly known as Little River Turnpike, connecting Fairfax and Alexandria.
-
B.
SR 263
SR 263 is a state highway in Maine that serves as a short connector route within the state's numbered road network.
-
C.
SR 230
SR 230 is a primary state highway in Virginia that connects U.S. Route 29 near Madison to U.S. Route 33 near Stanardsville, serving rural communities in Madison and Greene counties.
-
D.
SR 230
SR 230 is a state highway in Maine that serves as a short connector route in the coastal Downeast region.
-
E.
SR 233
SR 233 is a state highway in Maine that serves as a connector route on Mount Desert Island, providing access between Bar Harbor and other parts of the island.
- 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_69e11e5657e881909f16ca58352c50da |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15e34590c81909e4ed1c95f13a199 |
completed | April 29, 2026, 1:26 a.m. |
Created at: April 16, 2026, 8:50 p.m.