Triple
T5151626
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saale |
E116207
|
entity |
| Predicate | hasTributary |
P415
|
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: [Saale, hasTributary, Bode]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Bode Context triple: [Saale, hasTributary, 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.
Boe
Boe is a city in Guinea-Bissau known as the site where the Boé Declaration on Regional Security was adopted.
-
D.
Royer
Royer was a costume designer known for his work on classic Hollywood films, including the 1939 drama "The Rains Came."
-
E.
Bortus
Bortus is a stoic, duty-bound Moclan officer serving as second-in-command aboard the exploratory spaceship in the sci-fi comedy series "The Orville."
- 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_69bd445d94788190b72e2cc563120995 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd78d965548190b09f574acf3b9b1a |
completed | March 20, 2026, 4:42 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69bed004538c81908fac258ea99f7e63 |
completed | March 21, 2026, 5:06 p.m. |
Created at: March 20, 2026, 1:44 p.m.