Triple
T21748596
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District of Coburg |
E536850
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Weitramsdorf |
—
|
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: Weitramsdorf | Statement: [District of Coburg, hasMunicipality, Weitramsdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Weitramsdorf Context triple: [District of Coburg, hasMunicipality, Weitramsdorf]
-
A.
Weitramsdorf
chosen
Weitramsdorf is a municipality in the Coburg district of northern Bavaria, Germany, known for its rural character and proximity to the city of Coburg.
-
B.
Rathmannsdorf
Rathmannsdorf is a small municipality in the German state of Saxony, known for its location in the scenic Saxon Switzerland region.
-
C.
Burkhardtsdorf
Burkhardtsdorf is a small municipality in the Erzgebirge (Ore Mountains) region of Saxony, eastern Germany.
-
D.
Rittersdorf
Rittersdorf is a small municipality located in the Weimarer Land district of the German federal state of Thuringia.
-
E.
Stuhmsdorf
Stuhmsdorf is a village in northern Poland historically notable as the site where the 1635 Treaty of Stuhmsdorf was concluded between the Polish–Lithuanian Commonwealth and Sweden.
- 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a77e19c81909bf26f96aa41a7ce |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 16, 2026, 6:50 p.m.