Triple
T12033262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Route 316 |
E286464
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | GA 316 |
E128438
|
NE FINISHED |
How this triple was built (2 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: GA 316 | Statement: [State Route 316, abbreviation, GA 316]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GA 316 Context triple: [State Route 316, abbreviation, GA 316]
-
A.
GA 400
GA 400 is a major north–south freeway in Georgia that connects downtown Atlanta with its northern suburbs and exurbs.
-
B.
GA 16
GA 16 is a state highway in Georgia that runs east–west across the central part of the state, connecting several towns and major routes.
-
C.
GA-316
chosen
GA-316 is a major east–west state highway in Georgia that connects the Atlanta metropolitan area with the city of Athens.
-
D.
GA 100
GA 100 is a state highway in Georgia that runs north–south through several counties, connecting small towns and local communities.
-
E.
GA 85
GA 85 is a state highway in Georgia that runs generally south–north, connecting rural communities and suburbs to the Atlanta metropolitan area.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6ab4669e48190b59246358b0383ab |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9040724ec8190808f334013ddc6d6 |
completed | April 10, 2026, 2:07 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f49d6ec4b8819093ff50254a851444 |
completed | May 1, 2026, 12:32 p.m. |
Created at: April 8, 2026, 9:47 p.m.