Triple
T6709212
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 134 |
E153087
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 134
SR 134 is a state highway designation used for specific numbered routes within a U.S. state's road network.
|
E613823
|
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 134 | Statement: [State Route 134, abbreviation, SR 134]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 134 Context triple: [State Route 134, abbreviation, SR 134]
-
A.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
-
B.
SR 124
SR 124 is a state highway in Georgia that serves as an important regional connector through several suburban and semi-rural communities northeast of Atlanta.
-
C.
SR 143
SR 143 is a short Arizona state highway in the Phoenix metropolitan area that primarily serves as a connector between Interstate 10 and Phoenix Sky Harbor International Airport.
-
D.
SR 14
SR 14 is a state highway in Georgia that serves as a key transportation route connecting several communities in the western part of the state.
-
E.
SR 138
SR 138 is a state highway in Georgia that runs east–west through several counties in the Atlanta metropolitan area, serving as a key regional connector.
- 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 134 Triple: [State Route 134, abbreviation, SR 134]
Generated description
SR 134 is a state highway designation used for specific numbered routes within a U.S. state's road network.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 134 Target entity description: SR 134 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
A.
SR 113
SR 113 is a state highway in northern Ohio that runs east–west through several counties, connecting rural areas with small towns and cities.
-
B.
SR 124
SR 124 is a state highway in Georgia that serves as an important regional connector through several suburban and semi-rural communities northeast of Atlanta.
-
C.
SR 143
SR 143 is a short Arizona state highway in the Phoenix metropolitan area that primarily serves as a connector between Interstate 10 and Phoenix Sky Harbor International Airport.
-
D.
SR 14
SR 14 is a state highway in Georgia that serves as a key transportation route connecting several communities in the western part of the state.
-
E.
SR 138
SR 138 is a state highway in Georgia that runs east–west through several counties in the Atlanta metropolitan area, serving as a key regional connector.
- 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_69c68808d8d8819087369015270788fe |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d105b49c8190932246a727e2c513 |
completed | March 27, 2026, 6:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c7008e6b308190a3d5db2bf4a469c4 |
completed | March 27, 2026, 10:11 p.m. |
| NEDg | Description generation | batch_69c701be78cc8190a0848ea60908d129 |
completed | March 27, 2026, 10:16 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69c7021b27288190866aef500198479d |
completed | March 27, 2026, 10:18 p.m. |
Created at: March 27, 2026, 2:06 p.m.