Triple
T15106446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stahnsdorf South-Western Cemetery |
E360798
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Stahnsdorf |
E1082968
|
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: Stahnsdorf | Statement: [Stahnsdorf South-Western Cemetery, locatedIn, Stahnsdorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Stahnsdorf Context triple: [Stahnsdorf South-Western Cemetery, locatedIn, Stahnsdorf]
-
A.
Stahnsdorf
chosen
Stahnsdorf is a municipality in the Potsdam-Mittelmark district of Brandenburg, Germany, known for its large forest cemetery and its location on the southwestern outskirts of Berlin.
-
B.
Stolzenhagen
Stolzenhagen is a village and locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
-
C.
Schorfheide
Schorfheide is a large forested and lake-rich area in Brandenburg, Germany, known for its protected natural landscapes and historical use as a royal and political hunting ground.
-
D.
Schönwalde
Schönwalde is a locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
-
E.
Stedesdorf
Stedesdorf is a small municipality in Lower Saxony, Germany, situated in the East Frisian region.
- 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_69d85a0491ec8190830960be8fafb994 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00588f35481909674f161bf0f3918 |
completed | April 15, 2026, 9:39 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fef88bc8088190a357657c461f761d |
completed | May 9, 2026, 9:04 a.m. |
Created at: April 10, 2026, 3:05 a.m.