Triple
T8254412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dahlonega |
E193034
|
entity |
| Predicate | hasNickname |
P39
|
FINISHED |
| Object | Gold City |
E220228
|
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: Gold City | Statement: [Dahlonega, hasNickname, Gold City]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Gold City Context triple: [Dahlonega, hasNickname, Gold City]
-
A.
Gold City
chosen
Gold City is a nickname for Dahlonega, Georgia, a historic town famed for its early 19th-century gold rush and mining heritage.
-
B.
Gold Point
Gold Point is a historic Nevada mining ghost town known for its preserved old buildings and Wild West heritage.
-
C.
Golden City
Golden City is a poetic nickname for Prague, highlighting the city's historic skyline of gilded spires and sunlit architecture.
-
D.
Golden City
Golden City is a small rural town in Barton County, southwestern Missouri, known for its agricultural surroundings and tight-knit community.
-
E.
Golden City
Golden City is the popular nickname for Jaisalmer, a historic sandstone city in the Thar Desert of Rajasthan, India, famed for its golden-hued fort and architecture.
- 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_69ca82dfad9c8190b8cd18fb89f50f40 |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb78f8eccc8190b43204bf2f8defc1 |
completed | March 31, 2026, 7:34 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cd354a412c8190963605d177d94a17 |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 5:48 p.m.