Triple
T17812626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haselhorst |
E444749
|
entity |
| Predicate | adjacentTo |
P224
|
FINISHED |
| Object | Hakenfelde |
—
|
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: Hakenfelde | Statement: [Haselhorst, adjacentTo, Hakenfelde]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Hakenfelde Context triple: [Haselhorst, adjacentTo, Hakenfelde]
-
A.
Hakenfelde
chosen
Hakenfelde is a locality in the Berlin borough of Spandau, known for its residential areas, green spaces, and proximity to the Havel River.
-
B.
Ruhmannsfelden
Ruhmannsfelden is a small market town in the Bavarian Forest region of southeastern Germany.
-
C.
Hellefeld
Hellefeld is a village and district within the town of Sundern in the Hochsauerland region of North Rhine-Westphalia, Germany.
-
D.
Heckfeld
Heckfeld is a village and district of the town Lauda-Königshofen in the Main-Tauber region of Baden-Württemberg, Germany.
-
E.
Dahenfeld
Dahenfeld is a village and district of the town of Neckarsulm in the German state of Baden-Württemberg.
- 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_69d8b9f0de78819099395b14db75a8a6 |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4887c63608190b29a407cabff0bc5 |
completed | April 19, 2026, 7:47 a.m. |
Created at: April 10, 2026, 10:14 a.m.