Triple
T10968517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Waldeck-Frankenberg |
E259169
|
entity |
| Predicate | containsMunicipality |
P852
|
FINISHED |
| Object | Allendorf (Eder) |
E880173
|
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: Allendorf (Eder) | Statement: [Waldeck-Frankenberg, containsMunicipality, Allendorf (Eder)]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Allendorf (Eder) Context triple: [Waldeck-Frankenberg, containsMunicipality, Allendorf (Eder)]
-
A.
Allendorf
chosen
Allendorf is a village-level subdivision of the town of Sundern in the Hochsauerland district of North Rhine-Westphalia, Germany.
-
B.
Stadtallendorf
Stadtallendorf is a town in the German state of Hesse known for its industrial history and role as a regional economic center.
-
C.
Offendorf
Offendorf is a small commune in northeastern France’s Alsace region, situated along the Rhine and known for its riverside setting and traditional village character.
-
D.
Westendorf
Westendorf is a popular Austrian alpine village known for its skiing, hiking, and picturesque mountain scenery.
-
E.
Nordendorf
Nordendorf is a small municipality in Bavaria, Germany, situated within the Augsburg district.
- 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_69d6aa895f4c8190887a15460ef622f4 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7719800388190943a0bffa48a2731 |
completed | April 9, 2026, 9:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e2d78156c48190a956dc22b9832bcb |
completed | April 18, 2026, 12:59 a.m. |
Created at: April 8, 2026, 9:24 p.m.