Triple
T20826207
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kippenheim |
E512705
|
entity |
| Predicate | hasNeighbouringMunicipality |
P224
|
FINISHED |
| Object | Friesenheim |
—
|
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: Friesenheim | Statement: [Kippenheim, hasNeighbouringMunicipality, Friesenheim]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Friesenheim Context triple: [Kippenheim, hasNeighbouringMunicipality, Friesenheim]
-
A.
Friesenheim
chosen
Friesenheim is a municipality in the Ortenau district of the state of Baden-Württemberg in southwestern Germany.
-
B.
Friesenheim
Friesenheim is a district of the industrial city of Ludwigshafen am Rhein in the German state of Rhineland-Palatinate.
-
C.
Friemersheim
Friemersheim is a district within the Rheinhausen area of Duisburg in North Rhine-Westphalia, Germany, known for its historical roots and residential character.
-
D.
Frankenheim
Frankenheim is a village in the Rhön region of Bavaria, Germany, known for its rural setting within the municipality of Bischofsheim an der Rhön.
-
E.
Willebadessen
Willebadessen is a small town in western Germany, located in the state of North Rhine-Westphalia.
- 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_69e0b4ce39108190a6e8e5df4f1c8dc5 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2fd8480819099930af691d97477 |
completed | April 21, 2026, 12:21 a.m. |
Created at: April 16, 2026, 12:41 p.m.