Triple
T16504191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Delme |
E400878
|
entity |
| Predicate | flowsInto |
P408
|
FINISHED |
| Object | Ochtum |
E369362
|
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: Ochtum | Statement: [Delme, flowsInto, Ochtum]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Ochtum Context triple: [Delme, flowsInto, Ochtum]
-
A.
Ochtum
chosen
The Ochtum is a river in northwestern Germany that flows through Lower Saxony and Bremen before joining the Weser.
-
B.
Rakhumai
Rakhumai is a revered Hindu goddess worshipped as the compassionate consort of Vithoba (a form of Krishna/Vishnu) at the famous Pandharpur temple in Maharashtra.
-
C.
Yasa'ur
Yasa'ur was a Mongol prince and military leader who played a significant role in the politics and conflicts of the Chagatai Khanate during the early 14th century.
-
D.
Othomi
Othomi is an alternative name for the Otomi people and their indigenous language of central Mexico.
-
E.
The Turim
The Turim is a foundational 14th-century Jewish legal code by Rabbi Jacob ben Asher that systematically organizes halakhic rulings into four major sections.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e5100e48190a623d6ee2fefb87e |
completed | April 18, 2026, 7:10 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0067a31c8881909b05c49c8006785d |
completed | May 10, 2026, 11:10 a.m. |
Created at: April 10, 2026, 5:14 a.m.