Triple
T18438994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Marzahn-Hellersdorf |
E450473
|
entity |
| Predicate | hasSubdistrict |
P747
|
FINISHED |
| Object | Biesdorf |
—
|
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: Biesdorf | Statement: [Marzahn-Hellersdorf, hasSubdistrict, Biesdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Biesdorf Context triple: [Marzahn-Hellersdorf, hasSubdistrict, Biesdorf]
-
A.
Biesdorf
chosen
Biesdorf is a residential district in eastern Berlin, Germany, known for its mix of post-war housing estates, green spaces, and historic village core.
-
B.
Bohnsdorf
Bohnsdorf is a residential locality in the southeastern part of Berlin, Germany, known for its suburban character and proximity to the city’s green and lake-rich areas.
-
C.
Basdorf
Basdorf is a village and district within the municipality of Wandlitz in the state of Brandenburg, Germany.
-
D.
Wiesdorf
Wiesdorf is a central district of the German city of Leverkusen, known for its commercial areas and proximity to major industrial facilities.
-
E.
Biendorf
Biendorf is a small municipality in northern Germany notable as the birthplace of German Field Marshal Helmuth von Moltke the Younger.
- 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_69d8d381d6388190a9e94e9c658174e4 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e51c0ed6708190ae90efd8455ec352 |
completed | April 19, 2026, 6:16 p.m. |
Created at: April 10, 2026, 11:30 a.m.