Triple
T23471764
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Neckar-Odenwald-Kreis |
E570147
|
entity |
| Predicate | hasMunicipality |
P847
|
FINISHED |
| Object | Adelsheim |
—
|
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: Adelsheim | Statement: [Neckar-Odenwald-Kreis, hasMunicipality, Adelsheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Adelsheim Context triple: [Neckar-Odenwald-Kreis, hasMunicipality, Adelsheim]
-
A.
Adelsheim
chosen
Adelsheim is a small town in the Neckar-Odenwald district of Baden-Württemberg in southwestern Germany.
-
B.
Blodelsheim
Blodelsheim is a commune in the Haut-Rhin department of the Grand Est region in northeastern France.
-
C.
Riedisheim
Riedisheim is a commune in northeastern France’s Grand Est region, situated near the city of Mulhouse in the Haut-Rhin department.
-
D.
Heroldsberg
Heroldsberg is a municipality in the Erlangen-Höchstadt district of Bavaria, Germany, known for its historic center and proximity to the city of Nuremberg.
-
E.
Winzenheim
Winzenheim is a district of the town of Bad Kreuznach in the German state of Rhineland-Palatinate.
- 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_69e245af8a88819084f2704f6d265a92 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a700bd0481908047aa4678217cbd |
completed | April 29, 2026, 6:36 a.m. |
Created at: April 17, 2026, 5:55 p.m.