Triple
T22795199
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 188 (Georgia) |
E564222
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 188
SR 188 is a state highway in Georgia that serves as a regional connector route through several rural communities.
|
E1555997
|
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 188 | Statement: [State Route 188 (Georgia), abbreviation, SR 188]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 188 Context triple: [State Route 188 (Georgia), abbreviation, SR 188]
-
A.
SR 188
SR 188 is a short California state highway that connects the city of Tecate to the U.S.–Mexico border in San Diego County.
-
B.
SR 188
SR 188 is a state highway in Ohio that connects several communities in the central part of the state.
-
C.
SR 188
SR 188 is a state highway in Maine that serves as a regional connector route through Penobscot County.
-
D.
SR 181
SR 181 is a state highway in Maine that serves as a regional connector route through Hancock County.
-
E.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. 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 188 Triple: [State Route 188 (Georgia), abbreviation, SR 188]
Generated description
SR 188 is a state highway in Georgia that serves as a regional connector route through several rural communities.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 188 Target entity description: SR 188 is a state highway in Georgia that serves as a regional connector route through several rural communities.
-
A.
SR 188
SR 188 is a short California state highway that connects the city of Tecate to the U.S.–Mexico border in San Diego County.
-
B.
SR 188
SR 188 is a state highway in Ohio that connects several communities in the central part of the state.
-
C.
SR 188
SR 188 is a state highway in Maine that serves as a regional connector route through Penobscot County.
-
D.
SR 181
SR 181 is a state highway in Maine that serves as a regional connector route through Hancock County.
-
E.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. 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_69e2458185f88190b0045227ee420411 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17cd8e0c4819086da0488bea56a34 |
completed | April 29, 2026, 3:36 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0b9e93d1588190a221906ce5a4d834 |
completed | May 18, 2026, 11:19 p.m. |
| NEDg | Description generation | batch_6a0ba2ab22848190a11ebb3514d416f4 |
completed | May 18, 2026, 11:37 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0ba33d87248190ad15c4c72c671fec |
completed | May 18, 2026, 11:39 p.m. |
Created at: April 17, 2026, 3:30 p.m.