Triple
T9084098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ralf D. Bode |
E217705
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Bode |
E84164
|
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: [Ralf D. Bode, familyName, Bode]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bode Context triple: [Ralf D. Bode, familyName, Bode]
-
A.
Bode
The Bode is a river in central Germany that flows through the Harz Mountains and Saxony-Anhalt before joining the Saale.
-
B.
Bode
chosen
Bode is a surname most notably associated with Hendrik Wade Bode, an influential American engineer and pioneer in control theory and communication systems.
-
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.
Burrus
Burrus is a variant form of the name Burr, used as a personal or family name.
-
E.
Boe
Boe is a city in Guinea-Bissau known as the site where the Boé Declaration on Regional Security was adopted.
- 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_69ca83d7a0388190ba1af89ed7ba36f9 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc960b45fc8190adf4bdc41b103e86 |
completed | April 1, 2026, 3:50 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cffe38f0048190a9fb15e73d9bcd50 |
completed | April 3, 2026, 5:51 p.m. |
Created at: March 30, 2026, 7:13 p.m.