Triple
T15049661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nienburg (Saale) |
E379321
|
entity |
| Predicate | hasNearbyWaterBody |
P1489
|
FINISHED |
| Object | Bode |
E78295
|
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: Bode | Statement: [Nienburg (Saale), hasNearbyWaterBody, Bode]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bode Context triple: [Nienburg (Saale), hasNearbyWaterBody, Bode]
-
A.
Bode
Bode is a surname most notably associated with Hendrik Wade Bode, an influential American engineer and pioneer in control theory and communication systems.
-
B.
Bode
chosen
The Bode is a river in central Germany that flows through the Harz Mountains and Saxony-Anhalt before joining the Saale.
-
C.
Bonger
Bonger is a Dutch surname most notably associated with Johanna van Gogh-Bonger, the key figure in preserving and promoting Vincent van Gogh’s artistic legacy.
-
D.
Bode (nearby)
Bode (nearby) is a river in the Harz region of central Germany, known for flowing through scenic gorges and valleys before joining the Saale.
-
E.
Burrus
Burrus is a variant form of the name Burr, used as a personal or family name.
- 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_69d85cd64d108190853797a95c11cc45 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69deda8f71988190b4fe7f7de4ccb798 |
completed | April 15, 2026, 12:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69febfd954548190b3f7c60d95403f3e |
completed | May 9, 2026, 5:02 a.m. |
Created at: April 10, 2026, 3 a.m.