Triple
T10712692
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 24 |
E252579
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object |
SR 24
SR 24 is a state highway in Georgia that runs generally southeast–northwest, connecting several cities and rural areas across the state.
|
E881030
|
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 24 | Statement: [Georgia State Route 24, abbreviation, SR 24]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: SR 24 Context triple: [Georgia State Route 24, abbreviation, SR 24]
-
A.
SR 24
SR 24 is a Florida state highway that runs east–west, connecting the Gulf Coast near Cedar Key to Gainesville and other inland communities.
-
B.
SR 242
SR 242 is a state highway designated as State Route 242 within a U.S. state’s numbered road network.
-
C.
SR 243
SR 243 is a short primary state highway in Fairfax County, Virginia, serving as a connector route in the suburban Washington, D.C. metropolitan area.
-
D.
SR 28
SR 28 is a scenic Nevada state highway that runs along the northeastern shore of Lake Tahoe, connecting U.S. Route 50 near Spooner Lake to the California state line.
-
E.
SR 28
SR 28 is a primary state highway in Virginia that serves as a major north–south transportation corridor in the northern part of the state.
- 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 24 Triple: [Georgia State Route 24, abbreviation, SR 24]
Generated description
SR 24 is a state highway in Georgia that runs generally southeast–northwest, connecting several cities and rural areas across the state.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: SR 24 Target entity description: SR 24 is a state highway in Georgia that runs generally southeast–northwest, connecting several cities and rural areas across the state.
-
A.
SR 24
SR 24 is a Florida state highway that runs east–west, connecting the Gulf Coast near Cedar Key to Gainesville and other inland communities.
-
B.
SR 242
SR 242 is a state highway designated as State Route 242 within a U.S. state’s numbered road network.
-
C.
SR 243
SR 243 is a short primary state highway in Fairfax County, Virginia, serving as a connector route in the suburban Washington, D.C. metropolitan area.
-
D.
SR 28
SR 28 is a scenic Nevada state highway that runs along the northeastern shore of Lake Tahoe, connecting U.S. Route 50 near Spooner Lake to the California state line.
-
E.
SR 28
SR 28 is a primary state highway in Virginia that serves as a major north–south transportation corridor in the northern part of the state.
- 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_69d6aa5cbabc8190973e683950d89faf |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6fe533ec081909eafab85f6f6d6b9 |
completed | April 9, 2026, 1:18 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d99917df2c819099be2a9b9c4a2ce7 |
completed | April 11, 2026, 12:43 a.m. |
| NEDg | Description generation | batch_69d99e86e198819080f71400295a31e7 |
completed | April 11, 2026, 1:06 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69dadccd1d7081908ae53b97d2c2a6cb |
completed | April 11, 2026, 11:44 p.m. |
Created at: April 8, 2026, 9:13 p.m.