Triple
T16549398
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Birkenwerder |
E402028
|
entity |
| Predicate | hasBorderWith |
P224
|
FINISHED |
| Object | Leegebruch |
E380241
|
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: Leegebruch | Statement: [Birkenwerder, hasBorderWith, Leegebruch]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Leegebruch Context triple: [Birkenwerder, hasBorderWith, Leegebruch]
-
A.
Leegebruch
chosen
Leegebruch is a small municipality in the German state of Brandenburg, located in the Oberhavel district just north of Berlin.
-
B.
Bruch
Bruch is a German surname most famously associated with the Romantic composer Max Bruch.
-
C.
Keutenberg
Keutenberg is a famously steep and decisive hill in the Dutch Limburg region, often shaping the outcome of professional cycling races.
-
D.
Schlegelberger
Schlegelberger is a German surname most notably associated with Franz Schlegelberger, a high-ranking Nazi-era jurist and acting Reich Minister of Justice.
-
E.
Hurwitz
Hurwitz is a surname of German and Ashkenazi Jewish origin borne by various notable individuals across fields such as mathematics, music, and law.
- 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_69d88384bc30819084229e7dcdc39a41 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e34fc323a88190b5c2a34de0a3c7f0 |
completed | April 18, 2026, 9:32 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067b6ca44819085145eb48356e7b4 |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:15 a.m.