Triple
T18459712
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rheinbach |
E450998
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Wormersdorf |
—
|
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: Wormersdorf | Statement: [Rheinbach, hasSubdivision, Wormersdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wormersdorf Context triple: [Rheinbach, hasSubdivision, Wormersdorf]
-
A.
Wormersdorf
chosen
Wormersdorf is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
-
B.
Landersdorf
Landersdorf is a locality within the city of Krems an der Donau in Lower Austria, known as part of its surrounding wine-growing and rural area.
-
C.
Wermsdorf
Wermsdorf is a municipality in Saxony, Germany, best known as the site of the large Baroque hunting lodge and former royal residence Hubertusburg Palace.
-
D.
Weisendorf
Weisendorf is a small municipality in the Erlangen-Höchstadt district of Bavaria, Germany, known for its rural character and proximity to the city of Erlangen.
-
E.
Plittersdorf
Plittersdorf is a village and district of the town of Rastatt in the state of Baden-Württemberg in southwestern Germany.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e52a7cdb5c8190a399f0e4052f7d1f |
completed | April 19, 2026, 7:18 p.m. |
Created at: April 10, 2026, 11:33 a.m.