Triple
T29477714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Auraria, Georgia |
E747693
|
entity |
| Predicate | hasNearbyHistoricCommunity |
P4647
|
FINISHED |
| Object | Dahlonega, Georgia |
—
|
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: Dahlonega, Georgia | Statement: [Auraria, Georgia, hasNearbyHistoricCommunity, Dahlonega, Georgia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyHistoricCommunity Context triple: [Auraria, Georgia, hasNearbyHistoricCommunity, Dahlonega, Georgia]
-
A.
hasNearbyHistoricArea
Indicates that one entity is located close to another entity that is designated as a historic area.
-
B.
hasNearbyCommunity
chosen
Indicates that one entity has another community located close to it in geographic or spatial terms.
-
C.
nearbyHistoricalServiceFor
Indicates that a historical service or facility is located close to a given reference entity or location.
-
D.
hasHistoricCommunity
Indicates that an entity is associated with, contains, or is part of a community of historical significance.
-
E.
neighboringHistoricGroup
Indicates that one historic group is geographically adjacent or directly next to another historic group.
- F. None of above.
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_69f0bd42cf308190bb01b20bc5b7c2d0 |
completed | April 28, 2026, 1:59 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
Created at: April 28, 2026, 4:01 p.m.