Triple
T20322546
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fairburn, Georgia |
E492241
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Union City, Georgia |
E79499
|
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: Union City, Georgia | Statement: [Fairburn, Georgia, adjacentTo, Union City, Georgia]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Union City, Georgia Context triple: [Fairburn, Georgia, adjacentTo, Union City, Georgia]
-
A.
Union City, Georgia
chosen
Union City, Georgia is a suburban city in the Atlanta metropolitan area located in Fulton County.
-
B.
Colquitt, Georgia
Colquitt, Georgia is a small city in southwest Georgia known as the cultural and economic hub of Miller County.
-
C.
Sylvania, Georgia
Sylvania, Georgia is a small city in Screven County known as the county seat and a historic community in eastern Georgia.
-
D.
Meansville, Georgia
Meansville, Georgia is a small rural town in Pike County known for its quiet residential character and location along regional routes in west-central Georgia.
-
E.
Lumber City, Georgia
Lumber City, Georgia is a small rural city in Telfair County known historically as a timber and river trade community in southeastern Georgia.
- 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_69e0b4a0134081909113563e1c3ba68a |
completed | April 16, 2026, 10:06 a.m. |
| NER | Named-entity recognition | batch_69e6778d95dc81909b1c87d26b5d3a33 |
completed | April 20, 2026, 6:59 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a08694d9d80819086ba91e8763c6b50 |
completed | May 16, 2026, 12:55 p.m. |
Created at: April 16, 2026, 11:20 a.m.