Triple
T9824296
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California State Route 238 |
E238615
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 238
SR 238 is a state highway in California that runs through the East Bay region, connecting the cities of Fremont, Union City, Hayward, and San Leandro.
|
E822521
|
NE FINISHED |
How this triple was built (4 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 238 | Statement: [California State Route 238, abbreviation, SR 238]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 238 Context triple: [California State Route 238, abbreviation, SR 238]
-
A.
SR 243
SR 243 is a short primary state highway in Fairfax County, Virginia, serving as a connector route in the suburban Washington, D.C. metropolitan area.
-
B.
SR 236
SR 236 is a primary state highway in Northern Virginia commonly known as Little River Turnpike, connecting Fairfax and Alexandria.
-
C.
SR 234
SR 234 is a primary state highway in Virginia that serves as a major north–south route connecting the Manassas area with Interstate highways and surrounding communities in Northern Virginia.
-
D.
SR 242
SR 242 is a state highway designated as State Route 242 within a U.S. state’s numbered road network.
-
E.
SR 289
SR 289 is a state highway route, designated with the number 289, that forms part of a regional road network in its jurisdiction.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: SR 238 Triple: [California State Route 238, abbreviation, SR 238]
Generated description
SR 238 is a state highway in California that runs through the East Bay region, connecting the cities of Fremont, Union City, Hayward, and San Leandro.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 238 Target entity description: SR 238 is a state highway in California that runs through the East Bay region, connecting the cities of Fremont, Union City, Hayward, and San Leandro.
-
A.
SR 243
SR 243 is a short primary state highway in Fairfax County, Virginia, serving as a connector route in the suburban Washington, D.C. metropolitan area.
-
B.
SR 236
SR 236 is a primary state highway in Northern Virginia commonly known as Little River Turnpike, connecting Fairfax and Alexandria.
-
C.
SR 234
SR 234 is a primary state highway in Virginia that serves as a major north–south route connecting the Manassas area with Interstate highways and surrounding communities in Northern Virginia.
-
D.
SR 242
SR 242 is a state highway designated as State Route 242 within a U.S. state’s numbered road network.
-
E.
SR 289
SR 289 is a state highway route, designated with the number 289, that forms part of a regional road network in its jurisdiction.
- F. None of above. chosen
Provenance (5 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_69ca84e0dd1881909800765d1e21f735 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb316f8948190ada3738787a5cb6a |
completed | April 2, 2026, 12:06 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d1cc810bac8190a5ff94c0717e7706 |
completed | April 5, 2026, 2:44 a.m. |
| NEDg | Description generation | batch_69d1cd5a04fc8190a78a1459b78962b1 |
completed | April 5, 2026, 2:47 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d1cdca61d481909f3394bf593f0bfb |
completed | April 5, 2026, 2:49 a.m. |
Created at: March 30, 2026, 8:31 p.m.