Triple
T12591498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana State Road 3 |
E300613
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 3
SR 3 is a primary north–south state highway in Indiana that connects several cities and rural areas across the eastern part of the state.
|
E1002251
|
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 3 | Statement: [Indiana State Road 3, abbreviation, SR 3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 3 Context triple: [Indiana State Road 3, abbreviation, SR 3]
-
A.
SR 3
SR 3 is the internal designation for a major north–south state highway corridor in Alabama that largely follows the route of U.S. Route 31.
-
B.
SR 3
SR 3 is a state highway in Washington that runs along the Kitsap Peninsula, connecting the Bremerton area with U.S. Route 101 near Shelton.
-
C.
SR 30
SR 30 is a designation for a major Florida state highway that largely follows the Gulf Coast, including portions concurrent with U.S. Route 98.
-
D.
SR 32
SR 32 is a major east–west state highway in Ohio that spans much of the southern part of the state, connecting Cincinnati to the Ohio River valley and Appalachian regions.
-
E.
SR 31
SR 31 is a state highway in northeastern Washington that runs north–south from near the town of Metaline Falls to the Canadian border.
- 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 3 Triple: [Indiana State Road 3, abbreviation, SR 3]
Generated description
SR 3 is a primary north–south state highway in Indiana that connects several cities and rural areas across the eastern part of the state.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 3 Target entity description: SR 3 is a primary north–south state highway in Indiana that connects several cities and rural areas across the eastern part of the state.
-
A.
SR 3
SR 3 is the internal designation for a major north–south state highway corridor in Alabama that largely follows the route of U.S. Route 31.
-
B.
SR 3
SR 3 is a state highway in Washington that runs along the Kitsap Peninsula, connecting the Bremerton area with U.S. Route 101 near Shelton.
-
C.
SR 30
SR 30 is a designation for a major Florida state highway that largely follows the Gulf Coast, including portions concurrent with U.S. Route 98.
-
D.
SR 32
SR 32 is a major east–west state highway in Ohio that spans much of the southern part of the state, connecting Cincinnati to the Ohio River valley and Appalachian regions.
-
E.
SR 31
SR 31 is a state highway in northeastern Washington that runs north–south from near the town of Metaline Falls to the Canadian border.
- 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_69d7bde87b648190bcd0266e9efde098 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954cc6d3c81908fbb22601c46f3f7 |
completed | April 10, 2026, 7:51 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f684d8b8d081908f271e75e6472914 |
completed | May 2, 2026, 11:12 p.m. |
| NEDg | Description generation | batch_69f687fffe9c81909c58129162a0c231 |
completed | May 2, 2026, 11:25 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f688cc57048190ba7bacdcd6c0c182 |
completed | May 2, 2026, 11:29 p.m. |
Created at: April 9, 2026, 5:07 p.m.