Triple
T16108597
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 210 (California) |
E390808
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | SR 210 |
E993445
|
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 210 | Statement: [State Route 210 (California), alsoKnownAs, SR 210]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 210 Context triple: [State Route 210 (California), alsoKnownAs, SR 210]
-
A.
SR 210
chosen
SR 210 is a major California state highway forming part of the Foothill Freeway corridor across the Greater Los Angeles and Inland Empire regions.
-
B.
SR 210
SR 210 is a former state highway in Maine that once served as a short connector route in Hancock County.
-
C.
SR 21
SR 21 is a primary state highway in Alabama that runs north–south across the state, connecting several major towns and highways.
-
D.
SR 21
SR 21 is a Florida state highway that runs through the Jacksonville area, serving as a major north–south route connecting suburban communities and military installations.
-
E.
SR 20
SR 20 is a major east–west state highway in Florida that runs across the northern part of the state, connecting cities such as Tallahassee and Palatka.
- 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20165aa9c81908c5358cca2b0d0fe |
completed | April 17, 2026, 9:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fff79c74388190a10e0346426b0cbe |
completed | May 10, 2026, 3:12 a.m. |
Created at: April 10, 2026, 5 a.m.