Triple
T10950745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuhlsbüttel |
E258718
|
entity |
| Predicate | hasNeighbouringQuarter |
P96797
|
FINISHED |
| Object | Niendorf |
E258720
|
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: Niendorf | Statement: [Fuhlsbüttel, hasNeighbouringQuarter, Niendorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Niendorf Context triple: [Fuhlsbüttel, hasNeighbouringQuarter, Niendorf]
-
A.
Niendorf
chosen
Niendorf is a residential district in the northwestern part of Hamburg, Germany, known for its suburban character and proximity to Hamburg Airport.
-
B.
Endenich
Endenich is a district of Bonn, Germany, historically known as the place where composer Robert Schumann spent his final years and died in a mental asylum.
-
C.
Neuendorf
Neuendorf is a small village on the Baltic Sea island of Hiddensee in Germany, known for its traditional thatched houses and maritime character.
-
D.
Neudorf
Neudorf is a residential district of Strasbourg, France, known for its dense urban fabric, local commerce, and proximity to the city center.
-
E.
Nauendorf
Nauendorf is a village in the German state of Saxony-Anhalt that forms part of the town of Wettin-Löbejün.
- 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_69d6aa88500c819097d7032ca578e74f |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d770ed2f1c819081ec58457f57889d |
completed | April 9, 2026, 9:27 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3447d8cc88190a3e28f204a93a7d3 |
completed | April 18, 2026, 8:44 a.m. |
Created at: April 8, 2026, 9:23 p.m.