Triple
T15127208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ohio State Route 151 |
E361321
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 151
SR 151 is a state highway in Ohio that serves as a regional connector route through the eastern part of the state.
|
E1141974
|
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 151 | Statement: [Ohio State Route 151, abbreviation, SR 151]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 151 Context triple: [Ohio State Route 151, abbreviation, SR 151]
-
A.
SR 151
SR 151 is a state highway in Maine that runs through rural communities, connecting local roads to larger regional routes.
-
B.
SR 152
SR 152 is a major east–west state highway in California that connects the Central Coast region with the San Joaquin Valley, including a key pass over the Diablo Range.
-
C.
SR 152
SR 152 is a state highway in Maine that runs generally north–south, connecting several rural communities and serving as a regional connector route.
-
D.
SR 15
SR 15 is a state highway in Maine that runs through the city of Brewer and connects several communities in the region.
-
E.
SR 153
SR 153 is a state highway in Maine that serves as a short connector route within the state's road network.
- 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 151 Triple: [Ohio State Route 151, abbreviation, SR 151]
Generated description
SR 151 is a state highway in Ohio that serves as a regional connector route through the eastern part of the state.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 151 Target entity description: SR 151 is a state highway in Ohio that serves as a regional connector route through the eastern part of the state.
-
A.
SR 151
SR 151 is a state highway in Maine that runs through rural communities, connecting local roads to larger regional routes.
-
B.
SR 152
SR 152 is a major east–west state highway in California that connects the Central Coast region with the San Joaquin Valley, including a key pass over the Diablo Range.
-
C.
SR 152
SR 152 is a state highway in Maine that runs generally north–south, connecting several rural communities and serving as a regional connector route.
-
D.
SR 15
SR 15 is a state highway in Maine that runs through the city of Brewer and connects several communities in the region.
-
E.
SR 153
SR 153 is a state highway in Maine that serves as a short connector route within the state's road network.
- 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_69d85a06450081909c5a14ea9851a15e |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e005a1b9288190954f2d92549805e5 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fec87ed2cc8190b4cae72774e0df7f |
completed | May 9, 2026, 5:39 a.m. |
| NEDg | Description generation | batch_69fecbcd8d1881909706e7350e63e6c1 |
completed | May 9, 2026, 5:53 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69fecbf6751081908a97485497047e6c |
completed | May 9, 2026, 5:53 a.m. |
Created at: April 10, 2026, 3:06 a.m.