Triple
T12910367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texas State Highway 11 |
E308844
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SH 11
SH 11 is a Texas state highway that runs across the northeastern part of the state, connecting several rural communities and regional routes.
|
E1009828
|
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: SH 11 | Statement: [Texas State Highway 11, abbreviation, SH 11]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SH 11 Context triple: [Texas State Highway 11, abbreviation, SH 11]
-
A.
SH 114
SH 114 is a major Texas state highway running through the Dallas–Fort Worth area and connecting several key cities in North Texas.
-
B.
SH 12
SH 12 is a designation for Texas State Highway 12, a state-maintained roadway within the Texas highway system.
-
C.
SH 10
SH 10 is a state highway in Colorado that runs east–west across the southern part of the state, connecting the cities of Walsenburg and La Junta.
-
D.
SH 121
SH 121 is a state highway in Colorado that runs through the Denver metropolitan area, serving as a major north–south arterial route.
-
E.
SH 121
SH 121 is a major Texas state highway that serves as a key north–south and northeast–southwest transportation corridor through the Dallas–Fort Worth metropolitan area.
- 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: SH 11 Triple: [Texas State Highway 11, abbreviation, SH 11]
Generated description
SH 11 is a Texas state highway that runs across the northeastern part of the state, connecting several rural communities and regional routes.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SH 11 Target entity description: SH 11 is a Texas state highway that runs across the northeastern part of the state, connecting several rural communities and regional routes.
-
A.
SH 114
SH 114 is a major Texas state highway running through the Dallas–Fort Worth area and connecting several key cities in North Texas.
-
B.
SH 12
SH 12 is a designation for Texas State Highway 12, a state-maintained roadway within the Texas highway system.
-
C.
SH 10
SH 10 is a state highway in Colorado that runs east–west across the southern part of the state, connecting the cities of Walsenburg and La Junta.
-
D.
SH 121
SH 121 is a state highway in Colorado that runs through the Denver metropolitan area, serving as a major north–south arterial route.
-
E.
SH 121
SH 121 is a major Texas state highway that serves as a key north–south and northeast–southwest transportation corridor through the Dallas–Fort Worth metropolitan area.
- 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_69d7bdf92b588190acdf2a2291ac4590 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d9719e584c81909be1ac1366effca0 |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6a56b50b48190a0deefd491ed8c4a |
completed | May 3, 2026, 1:31 a.m. |
| NEDg | Description generation | batch_69f6a6db731c819091b96c4ed6a50f19 |
completed | May 3, 2026, 1:37 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f6a8a31264819082c1ce67eaa529cc |
completed | May 3, 2026, 1:45 a.m. |
Created at: April 9, 2026, 5:41 p.m.