Triple
T21205820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ankum |
E522576
|
entity |
| Predicate | locatedNear |
P294
|
FINISHED |
| Object | Bersenbrück |
—
|
NE NERFINISHED |
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: Bersenbrück | Statement: [Ankum, locatedNear, Bersenbrück]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bersenbrück Context triple: [Ankum, locatedNear, Bersenbrück]
-
A.
Bersenbrück
chosen
Bersenbrück is a small town in Lower Saxony, Germany, known for its historic abbey and its location on the river Hase.
-
B.
Brück
Brück is a small town in the Potsdam-Mittelmark district of the German state of Brandenburg.
-
C.
Kindelbrück
Kindelbrück is a small town in the German state of Thuringia, situated in the Unstrut river valley and known for its rural character and historical architecture.
-
D.
Warthbrücken
Warthbrücken is the German name for the Polish town of Koło, located in central Poland on the Warta River.
-
E.
Möckernbrücke
Möckernbrücke is a Berlin U-Bahn station and major interchange point located near the Landwehr Canal in the Kreuzberg district.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b5112d8881909510b2dcdc93106d |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e734342e9081909e241bed54dbc0b4 |
completed | April 21, 2026, 8:24 a.m. |
Created at: April 16, 2026, 3:20 p.m.