Triple
T4638612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 14 |
E101594
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
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.
|
E463543
|
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 14 | Statement: [Georgia State Route 14, abbreviation, SR 14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 14 Context triple: [Georgia State Route 14, abbreviation, SR 14]
-
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 18
SR 18 is a state highway in Georgia that runs east–west across the central part of the state, connecting several small towns and regional routes.
-
C.
SR 16
SR 16 is a state highway in Georgia that runs east–west across the central part of the state, connecting several towns and major routes.
-
D.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
E.
SR 11
SR 11 is a planned and partially completed state highway intended to serve as a transportation corridor within its 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 14 Triple: [Georgia State Route 14, abbreviation, SR 14]
Generated description
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.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 14 Target entity description: 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.
-
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 18
SR 18 is a state highway in Georgia that runs east–west across the central part of the state, connecting several small towns and regional routes.
-
C.
SR 16
SR 16 is a state highway in Georgia that runs east–west across the central part of the state, connecting several towns and major routes.
-
D.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
E.
SR 11
SR 11 is a planned and partially completed state highway intended to serve as a transportation corridor within its 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_69bd43d3bc7c81908f81fcf380476b0f |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd5a64214481908a207e8070cc7a45 |
completed | March 20, 2026, 2:32 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be103799108190a905c28cdf302aba |
completed | March 21, 2026, 3:27 a.m. |
| NEDg | Description generation | batch_69be11df2c388190aef95ba0bbf69376 |
completed | March 21, 2026, 3:34 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69be1236359c81909ca62102d549a6f5 |
completed | March 21, 2026, 3:36 a.m. |
Created at: March 20, 2026, 1:13 p.m.