Triple
T12253879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oberursel |
E292046
|
entity |
| Predicate | hasSuburb |
P747
|
FINISHED |
| Object | Oberstedten |
E797625
|
NE FINISHED |
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: Oberstedten | Statement: [Oberursel, hasSuburb, Oberstedten]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Oberstedten Context triple: [Oberursel, hasSuburb, Oberstedten]
-
A.
Oberstedten
chosen
Oberstedten is a district of the town Oberursel in Hesse, Germany, situated near the Taunus mountain range.
-
B.
Weiterstadt
Weiterstadt is a town in the German state of Hesse, located near Darmstadt and known for its residential areas and commercial centers.
-
C.
Höchheim
Höchheim is a small municipality in the Rhön-Grabfeld district of northern Bavaria, Germany.
-
D.
Obergum
Obergum is a small neighborhood or former village that is now part of the town of Winsum in the province of Groningen, the Netherlands.
-
E.
Borgholzhausen
Borgholzhausen is a small town in North Rhine-Westphalia, Germany, known for its location on the Teutoburg Forest and its historical ties to the former County of Ravensberg.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d6ab67950c8190be08450a06228c4b |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d91cc849308190b6ff416f8b4f01e8 |
completed | April 10, 2026, 3:52 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6f5b3ced0819083382a0aceda171a |
completed | May 3, 2026, 7:13 a.m. |
Created at: April 8, 2026, 9:52 p.m.