Triple
T18682398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Georgia State Route 14 |
E456766
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | GA 14 |
—
|
NE NERFINISHED |
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 14 | Statement: [Georgia State Route 14, abbreviation, GA 14]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: GA 14 Context triple: [Georgia State Route 14, abbreviation, GA 14]
-
A.
GA 14
chosen
GA 14 is a state highway in Georgia that serves as a key route connecting several cities and communities in the western part of the state.
-
B.
GA 4
GA 4 is a primary north–south state highway in Georgia that runs through the eastern part of the state, connecting several communities and major routes.
-
C.
GA 54
GA 54 is a state highway in Georgia that connects several communities in the western part of the state, including areas south of Atlanta.
-
D.
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.
-
E.
GA 138
GA 138 is a state highway in Georgia that runs east–west through several counties in the Atlanta metropolitan area, serving as a key regional connector.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8d391eb488190ac2e9abf5bf255e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e55b2906ec8190ad8db8e3ae6b2945 |
completed | April 19, 2026, 10:46 p.m. |
Created at: April 10, 2026, 11:49 a.m.