Triple
T13191058
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Melchow |
E313985
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bernau bei Berlin |
E311039
|
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: Bernau bei Berlin | Statement: [Melchow, locatedNear, Bernau bei Berlin]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bernau bei Berlin Context triple: [Melchow, locatedNear, Bernau bei Berlin]
-
A.
Bernau bei Berlin
chosen
Bernau bei Berlin is a historic town in the German state of Brandenburg, located just northeast of Berlin and known for its well-preserved medieval city walls.
-
B.
Neuenhagen bei Berlin
Neuenhagen bei Berlin is a municipality in the Märkisch-Oderland district of Brandenburg, Germany, located just east of Berlin and known as a residential suburb of the capital.
-
C.
Falkensee
Falkensee is a town in the Havelland district of Brandenburg, Germany, situated just west of Berlin and functioning largely as a residential suburb of the capital.
-
D.
Stolzenhagen
Stolzenhagen is a village and locality within the municipality of Wandlitz in the state of Brandenburg, Germany.
-
E.
Degendorf
Degendorf is a locality within the Bavarian town and district of Lichtenfels in 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_69d806ae1e08819090d95bfe1538cc17 |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69d98c600ab48190bcf84aaf5846fb4b |
completed | April 10, 2026, 11:48 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f7941e0560819080eee43a9ed0e1bb |
completed | May 3, 2026, 6:29 p.m. |
Created at: April 9, 2026, 9:15 p.m.