Triple
T15899154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Omo River |
E385538
|
entity |
| Predicate | hasTributary |
P415
|
FINISHED |
| Object |
Mago River
The Mago River is a river in southwestern Ethiopia that flows through the Omo Valley region and contributes to the Omo River system.
|
E1183140
|
NE FINISHED |
How this triple was built (4 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: Mago River | Statement: [Omo River, hasTributary, Mago River]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mago River Context triple: [Omo River, hasTributary, Mago River]
-
A.
Cordevole River
The Cordevole River is a mountain river in northeastern Italy that flows through the Dolomites before joining the Piave River.
-
B.
Mi River
The Mi River is a significant river in Hunan Province, China, known as one of the main tributaries feeding into the Xiang River system.
-
C.
Oglio River
The Oglio River is a major river in northern Italy that flows from the Alps through Lombardy before joining the Po River.
-
D.
Meschio River
The Meschio River is a watercourse in northeastern Italy that flows through the Veneto region before joining the Piave River.
-
E.
Metauro River
The Metauro River is a waterway in the Marche region of Italy, historically significant as the site of the Battle of the Metaurus during the Second Punic War.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Mago River Triple: [Omo River, hasTributary, Mago River]
Generated description
The Mago River is a river in southwestern Ethiopia that flows through the Omo Valley region and contributes to the Omo River system.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Mago River Target entity description: The Mago River is a river in southwestern Ethiopia that flows through the Omo Valley region and contributes to the Omo River system.
-
A.
Cordevole River
The Cordevole River is a mountain river in northeastern Italy that flows through the Dolomites before joining the Piave River.
-
B.
Mi River
The Mi River is a significant river in Hunan Province, China, known as one of the main tributaries feeding into the Xiang River system.
-
C.
Oglio River
The Oglio River is a major river in northern Italy that flows from the Alps through Lombardy before joining the Po River.
-
D.
Meschio River
The Meschio River is a watercourse in northeastern Italy that flows through the Veneto region before joining the Piave River.
-
E.
Metauro River
The Metauro River is a waterway in the Marche region of Italy, historically significant as the site of the Battle of the Metaurus during the Second Punic War.
- F. None of above. chosen
Provenance (5 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_69d86da5b800819083a31be937d738b0 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e1563bd0688190b6f7a695be0a4625 |
completed | April 16, 2026, 9:35 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ffb04d4d1c819091d9b3357ca0deca |
completed | May 9, 2026, 10:08 p.m. |
| NEDg | Description generation | batch_69ffb190ae4881909ac299dfa6e7d9b6 |
completed | May 9, 2026, 10:13 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ffb25747148190bc96cf19acf85e29 |
completed | May 9, 2026, 10:16 p.m. |
Created at: April 10, 2026, 4:51 a.m.