Triple
T6105437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 81 |
E136105
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 81
SR 81 is a state highway in Georgia that connects several communities in the eastern and north-central part of the state.
|
E568485
|
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 81 | Statement: [Georgia State Route 81, abbreviation, SR 81]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 81 Context triple: [Georgia State Route 81, abbreviation, SR 81]
-
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 108
SR 108 is a California state highway that traverses the Sierra Nevada, including the high-altitude Sonora Pass, connecting the Central Valley with the eastern side of the range.
-
C.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
D.
SR 88
SR 88 is a scenic California state highway that traverses the Sierra Nevada, connecting the Central Valley to mountain communities and recreational areas near the Nevada border.
-
E.
SR 168
SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
- 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 81 Triple: [Georgia State Route 81, abbreviation, SR 81]
Generated description
SR 81 is a state highway in Georgia that connects several communities in the eastern and north-central part of the state.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 81 Target entity description: SR 81 is a state highway in Georgia that connects several communities in the eastern and north-central part of the state.
-
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 108
SR 108 is a California state highway that traverses the Sierra Nevada, including the high-altitude Sonora Pass, connecting the Central Valley with the eastern side of the range.
-
C.
SR 180
SR 180 is a state highway designation used for specific numbered routes within a U.S. state's road network.
-
D.
SR 88
SR 88 is a scenic California state highway that traverses the Sierra Nevada, connecting the Central Valley to mountain communities and recreational areas near the Nevada border.
-
E.
SR 168
SR 168 is a state highway designated as State Route 168 within a U.S. state’s numbered road system.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b7ee8b48190b87f5ec8a46d6e2d |
completed | March 22, 2026, 9:13 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c1255759f48190a6aadf33406dcb49 |
completed | March 23, 2026, 11:34 a.m. |
| NEDg | Description generation | batch_69c1275910108190a0a5f458a468c292 |
completed | March 23, 2026, 11:43 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c127b831d081909436a62e002d1fa5 |
completed | March 23, 2026, 11:44 a.m. |
Created at: March 22, 2026, 4:13 p.m.