Triple
T13113854
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Panketal |
E311041
|
entity |
| Predicate | sharesBorderWith |
P224
|
FINISHED |
| Object | Wandlitz |
E311040
|
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: Wandlitz | Statement: [Panketal, sharesBorderWith, Wandlitz]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Wandlitz Context triple: [Panketal, sharesBorderWith, Wandlitz]
-
A.
Wandlitz
chosen
Wandlitz is a municipality in the German state of Brandenburg, known for its lakes, forests, and proximity to Berlin.
-
B.
Glienicke
Glienicke is a historic area in Berlin, Germany, known for its palaces, parks, and its location near the Glienicke Bridge over the Havel River.
-
C.
Fürstenwalde
Fürstenwalde is a town in eastern Germany’s Brandenburg region, known for its location on the River Spree and its historic churches and medieval architecture.
-
D.
Schwedt
Schwedt is a town in northeastern Germany, located on the Oder River near the Polish border, known for its industrial facilities and cross-border regional ties.
-
E.
Schönwalde
Schönwalde is a locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
- 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_69d806a872d08190a329806f8ff30df4 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d9817f8ee8819084078b4bec5e4f18 |
completed | April 10, 2026, 11:02 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fed314bb9481908144c5399aa62ffa |
completed | May 9, 2026, 6:24 a.m. |
Created at: April 9, 2026, 9:06 p.m.