Triple
T18804063
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eschborn |
E459827
|
entity |
| Predicate | hasCityDistrict |
P2709
|
FINISHED |
| Object | Niederhöchstadt |
—
|
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: Niederhöchstadt | Statement: [Eschborn, hasCityDistrict, Niederhöchstadt]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Niederhöchstadt Context triple: [Eschborn, hasCityDistrict, Niederhöchstadt]
-
A.
Hettstadt
Hettstadt is a small municipality in the Würzburg district of Bavaria, Germany, known for its rural character and proximity to the city of Würzburg.
-
B.
Höchheim
Höchheim is a small municipality in the Rhön-Grabfeld district of northern Bavaria, Germany.
-
C.
Oberhöchstadt
chosen
Oberhöchstadt is a district of the town of Kronberg im Taunus in Hesse, Germany, known for its residential character within the Taunus region.
-
D.
Weiterstadt
Weiterstadt is a town in the German state of Hesse, located near Darmstadt and known for its residential areas and commercial centers.
-
E.
Vellinghausen
Vellinghausen is a village in western Germany known historically as the site of the Battle of Vellinghausen during the Seven Years' War.
- 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_69d8d398c7d4819091cb2f7e48948aeb |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5a025faf48190be07086071df5b34 |
completed | April 20, 2026, 3:40 a.m. |
Created at: April 10, 2026, 11:53 a.m.