Triple
T6764380
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indiana State Road 56 |
E154679
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 56
SR 56 is a state highway in Indiana that runs east–west across the southern part of the state, connecting several towns and regional routes.
|
E618105
|
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 56 | Statement: [Indiana State Road 56, abbreviation, SR 56]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 56 Context triple: [Indiana State Road 56, abbreviation, SR 56]
-
A.
SR 55
SR 55 is a state highway in Georgia that serves as a regional connector route through several counties in the state.
-
B.
SR 57
SR 57 is a state highway in Ohio that serves as a regional connector route through several communities in the northern part of the state.
-
C.
SR 54
SR 54 is a state highway in Georgia that connects several communities in the western part of the state, including areas around Atlanta.
-
D.
SR 509
SR 509 is a state highway in Washington that serves as a key north–south route connecting cities in the Puget Sound region, including Tacoma and Seattle’s southern suburbs.
-
E.
SR 60
SR 60 is a major east–west freeway in Southern California that connects Los Angeles to the Inland Empire and serves as a key commuter and freight corridor.
- 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 56 Triple: [Indiana State Road 56, abbreviation, SR 56]
Generated description
SR 56 is a state highway in Indiana that runs east–west across the southern part of the state, connecting several towns and regional routes.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 56 Target entity description: SR 56 is a state highway in Indiana that runs east–west across the southern part of the state, connecting several towns and regional routes.
-
A.
SR 55
SR 55 is a state highway in Georgia that serves as a regional connector route through several counties in the state.
-
B.
SR 57
SR 57 is a state highway in Ohio that serves as a regional connector route through several communities in the northern part of the state.
-
C.
SR 54
SR 54 is a state highway in Georgia that connects several communities in the western part of the state, including areas around Atlanta.
-
D.
SR 509
SR 509 is a state highway in Washington that serves as a key north–south route connecting cities in the Puget Sound region, including Tacoma and Seattle’s southern suburbs.
-
E.
SR 60
SR 60 is a major east–west freeway in Southern California that connects Los Angeles to the Inland Empire and serves as a key commuter and freight corridor.
- 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_69c688109c1c8190added9a221292af0 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d217bbfc81908c9e55efaf7f8594 |
completed | March 27, 2026, 6:53 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c712b9e7f081909d9fcc219ac525b8 |
completed | March 27, 2026, 11:28 p.m. |
| NEDg | Description generation | batch_69c71396f1f88190b3316e694424a2fe |
completed | March 27, 2026, 11:32 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c7146413748190b844d9422dce42c2 |
completed | March 27, 2026, 11:36 p.m. |
Created at: March 27, 2026, 2:12 p.m.