Triple
T11758163
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SR 180 |
E279582
|
entity |
| Predicate | hasAbbreviation |
P43
|
FINISHED |
| Object |
SR-180
SR-180 is a state highway designation, likely referring to a specific numbered route within a U.S. state highway system.
|
E943648
|
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-180 | Statement: [SR 180, hasAbbreviation, SR-180]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR-180 Context triple: [SR 180, hasAbbreviation, SR-180]
-
A.
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.
-
B.
SR-91
SR-91 is a state highway designation commonly used in the United States for a numbered route within a state's road network.
-
C.
SR 400
SR 400 is a major north–south highway in Georgia that serves as a key commuter and traffic corridor through the Atlanta metropolitan area.
-
D.
SR 100
SR 100 is a state highway in Georgia that runs generally north–south, connecting several small towns and rural areas in the western part of the state.
-
E.
SR 100
SR 100 is a state highway designation commonly used in the United States for a numbered route within a 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-180 Triple: [SR 180, hasAbbreviation, SR-180]
Generated description
SR-180 is a state highway designation, likely referring to a specific numbered route within a U.S. state highway system.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR-180 Target entity description: SR-180 is a state highway designation, likely referring to a specific numbered route within a U.S. state highway system.
-
A.
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.
-
B.
SR-91
SR-91 is a state highway designation commonly used in the United States for a numbered route within a state's road network.
-
C.
SR 400
SR 400 is a major north–south highway in Georgia that serves as a key commuter and traffic corridor through the Atlanta metropolitan area.
-
D.
SR 100
SR 100 is a state highway in Georgia that runs generally north–south, connecting several small towns and rural areas in the western part of the state.
-
E.
SR 100
SR 100 is a state highway designation commonly used in the United States for a numbered route within a 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_69d6ab01038c819080714901502c84fc |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a5220f148190ae60d1941a579ab6 |
completed | April 10, 2026, 7:22 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f01a2f0a848190944ba2688c6d7ad2 |
completed | April 28, 2026, 2:23 a.m. |
| NEDg | Description generation | batch_69f03196d1608190999c505e96ce6be7 |
completed | April 28, 2026, 4:03 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69f05af9ce808190bc6c1ec2cb9903f9 |
completed | April 28, 2026, 7 a.m. |
Created at: April 8, 2026, 9:41 p.m.