Triple
T21368936
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | canton of Zug |
E526997
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Neuheim |
—
|
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: Neuheim | Statement: [canton of Zug, hasMunicipality, Neuheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Neuheim Context triple: [canton of Zug, hasMunicipality, Neuheim]
-
A.
Neuheim
chosen
Neuheim is a small Swiss municipality in the canton of Zug, known for its rural character and proximity to larger economic centers.
-
B.
Neuheim
Neuheim is a locality that forms part of the town of Jüterbog in the German state of Brandenburg.
-
C.
Neudorf
Neudorf is a residential district of Strasbourg, France, known for its dense urban fabric, local commerce, and proximity to the city center.
-
D.
Neudorf
Neudorf is a village-level subdivision of the Tyrolean municipality of Umhausen in western Austria.
-
E.
Neuenstein
Neuenstein is a small town in the Hohenlohe region of Baden-Württemberg, Germany, known for its historic castle and role as an administrative center.
- 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_69e0b51e80808190ba5cb05667af02a9 |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69ee5baf5fb4819093f8d8afdd83ffdb |
completed | April 26, 2026, 6:38 p.m. |
Created at: April 16, 2026, 5:09 p.m.