Triple
T19937900
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 18 |
E479222
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | SR 18 |
—
|
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 18 | Statement: [California State Route 18, abbreviation, SR 18]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 18 Context triple: [California State Route 18, abbreviation, SR 18]
-
A.
SR 18
SR 18 is a state highway in Georgia that runs east–west across the central part of the state, connecting several small towns and regional routes.
-
B.
SR 18
chosen
SR 18 is a California state highway that runs from San Bernardino through the San Bernardino Mountains to the High Desert, serving as a key route to communities like Crestline, Lake Arrowhead, and Victorville.
-
C.
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.
-
D.
SR 188
SR 188 is a state highway in Maine that serves as a regional connector route through Penobscot County.
-
E.
SR 188
SR 188 is a state highway in Ohio that connects several communities in the central part of the state.
- 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_69d8e522a17c819095165d4d24939fd8 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e65a190ac08190b9dc7955c9764a71 |
completed | April 20, 2026, 4:53 p.m. |
Created at: April 10, 2026, 1:53 p.m.