Triple
T16109038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 166 |
E390821
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 166
SR 166 is a state highway in Georgia that serves as a major east–west transportation corridor through the Atlanta metropolitan area and surrounding regions.
|
E1199255
|
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 166 | Statement: [Georgia State Route 166, abbreviation, SR 166]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 166 Context triple: [Georgia State Route 166, abbreviation, SR 166]
-
A.
SR 163
SR 163 is a major north–south freeway in San Diego, California, connecting downtown with the inland freeway network and passing through Balboa Park.
-
B.
SR 165
SR 165 is a state highway in Maine that serves as a regional connector route between several communities in the northern part of the state.
-
C.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
D.
SR 162
SR 162 is a state highway in Tennessee that serves as a key connector route in the Knoxville metropolitan area.
-
E.
SR 162
SR 162 is a state highway in Indiana that serves as a regional connector route through several southern Indiana communities.
- 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 166 Triple: [Georgia State Route 166, abbreviation, SR 166]
Generated description
SR 166 is a state highway in Georgia that serves as a major east–west transportation corridor through the Atlanta metropolitan area and surrounding regions.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 166 Target entity description: SR 166 is a state highway in Georgia that serves as a major east–west transportation corridor through the Atlanta metropolitan area and surrounding regions.
-
A.
SR 163
SR 163 is a major north–south freeway in San Diego, California, connecting downtown with the inland freeway network and passing through Balboa Park.
-
B.
SR 165
SR 165 is a state highway in Maine that serves as a regional connector route between several communities in the northern part of the state.
-
C.
SR 167
SR 167 is a state highway designation used for specific numbered routes within a U.S. state's transportation system.
-
D.
SR 162
SR 162 is a state highway in Indiana that serves as a regional connector route through several southern Indiana communities.
-
E.
SR 162
SR 162 is a state highway in Tennessee that serves as a key connector route in the Knoxville 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_69d87f1a8dd881909f1de6ef78849874 |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e20165aa9c81908c5358cca2b0d0fe |
completed | April 17, 2026, 9:46 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fffeef277481908ab35bbff06c827a |
completed | May 10, 2026, 3:43 a.m. |
| NEDg | Description generation | batch_6a0000ceba648190ac5ecefd34f10d4e |
completed | May 10, 2026, 3:51 a.m. |
| NED2 | Entity disambiguation (via description) | batch_6a00013fdb1c8190add653fc1cf30e44 |
completed | May 10, 2026, 3:53 a.m. |
Created at: April 10, 2026, 5 a.m.