Triple
T23135209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Treuchtlingen |
E577295
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Wettelsheim |
—
|
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: Wettelsheim | Statement: [Treuchtlingen, hasSubdivision, Wettelsheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wettelsheim Context triple: [Treuchtlingen, hasSubdivision, Wettelsheim]
-
A.
Wettelsheim
chosen
Wettelsheim is a small municipality in Bavaria, Germany, known for its rural character within the Weißenburg-Gunzenhausen region.
-
B.
Wollmesheim
Wollmesheim is a village and wine-growing district that forms part of the town of Landau in der Pfalz in the Rhineland-Palatinate region of Germany.
-
C.
Freiolsheim
Freiolsheim is a village and district of the town of Gaggenau in the Rastatt district of Baden-Württemberg, Germany.
-
D.
Bollwiller
Bollwiller is a commune in the Haut-Rhin department of the Grand Est region in northeastern France.
-
E.
Leutesheim
Leutesheim is a village and district of the town of Kehl in the Ortenaukreis region of Baden-Württemberg, Germany, near the Rhine River and the French border.
- 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_69e245f7b0e481909c473ff4e6a54e2c |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e8b694c8190b9ead00ea0576d90 |
completed | April 29, 2026, 4:52 a.m. |
Created at: April 17, 2026, 4 p.m.