Triple
T17665070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 203 |
E440356
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 203 |
E1169246
|
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 203 | Statement: [California State Route 203, abbreviation, SR 203]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 203 Context triple: [California State Route 203, abbreviation, SR 203]
-
A.
SR 203
chosen
SR 203 is a short state highway in Maine that connects local communities and provides regional access to larger routes.
-
B.
SR 205
SR 205 is a state highway in Maine that serves as a short connector route within the state's regional road network.
-
C.
SR 204
SR 204 is a state highway in Maine that serves as a local connector route on Mount Desert Island.
-
D.
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.
-
E.
SR 207
SR 207 is a state highway in Maine that serves as a regional connector route between local 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_69d8b9e87e18819087104a44dc4dc5b1 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e46ea8accc8190beea0900b0614020 |
completed | April 19, 2026, 5:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a023014a9d48190b7b5e86ce3bca3fd |
completed | May 11, 2026, 7:37 p.m. |
Created at: April 10, 2026, 9:56 a.m.