Triple
T21205263
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Iburg |
E522559
|
entity |
| Predicate | hasSubdivision |
P747
|
FINISHED |
| Object | Ostenfelde |
—
|
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: Ostenfelde | Statement: [Bad Iburg, hasSubdivision, Ostenfelde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ostenfelde Context triple: [Bad Iburg, hasSubdivision, Ostenfelde]
-
A.
Ostenfelde
chosen
Ostenfelde is a village in Germany best known as the birthplace of the influential 19th-century mathematician Karl Weierstrass.
-
B.
Ochsenfeld
Ochsenfeld is a German surname most notably borne by physicist Robert Ochsenfeld, known for his work on superconductivity.
-
C.
Todenfeld
Todenfeld is a village and district of the town of Rheinbach in the Rhein-Sieg-Kreis region of North Rhine-Westphalia, Germany.
-
D.
Sennfeld
Sennfeld is a municipality in the Schweinfurt district of Bavaria, Germany, known for its traditional Franconian character and proximity to the city of Schweinfurt.
-
E.
Pennenfeld
Pennenfeld is a residential subdistrict of the Bonn borough of Bad Godesberg in 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734342e9081909e241bed54dbc0b4 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 3:20 p.m.