Triple
T10063824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lichtenrade |
E213050
|
entity |
| Predicate | borderedBy |
P224
|
FINISHED |
| Object | Mariendorf |
E799064
|
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: Mariendorf | Statement: [Lichtenrade, borderedBy, Mariendorf]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mariendorf Context triple: [Lichtenrade, borderedBy, Mariendorf]
-
A.
Mariendorf
chosen
Mariendorf is a locality in the Tempelhof-Schöneberg borough of Berlin, Germany, known for its residential character and the historic Mariendorf trotting racetrack.
-
B.
Kleinmachnow
Kleinmachnow is a suburban municipality in the Potsdam-Mittelmark district of Brandenburg, Germany, located southwest of Berlin and known for its residential character and proximity to the capital.
-
C.
Wandlitz
Wandlitz is a municipality in the German state of Brandenburg, known for its lakes, forests, and proximity to Berlin.
-
D.
Langendorf
Langendorf is a municipality in the canton of Solothurn in northwestern Switzerland.
-
E.
Langendorf
Langendorf is a municipality in the Weißenfels area of Saxony-Anhalt in eastern 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_69ca83977128819084084eb7d1d8c52a |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdcfd4e4ac8190a37061b4082caa48 |
completed | April 2, 2026, 2:09 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d2b630ca008190a337660ad8c9d57e |
completed | April 5, 2026, 7:21 p.m. |
Created at: March 30, 2026, 8:58 p.m.