Triple
T33847024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nyangatóm |
E867508
|
entity |
| Predicate | usesRiverValley |
P27424
|
FINISHED |
| Object | Omo River |
—
|
NE NERFINISHED |
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: Omo River | Statement: [Nyangatóm, usesRiverValley, Omo River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRiverValley Context triple: [Nyangatóm, usesRiverValley, Omo River]
-
A.
hasRiverValley
Indicates that one location contains, includes, or is characterized by a river valley associated with another geographic feature or area.
-
B.
hasRiverValleyType
Indicates that an entity (such as a river or geographic area) is characterized by or associated with a specific type of river valley.
-
C.
locatedInRiverValley
chosen
Indicates that something is situated within the geographical area of a river valley.
-
D.
valleyRiver
Indicates that a river flows through, along, or is geographically associated with a particular valley.
-
E.
connectsRiverValley
Indicates a relationship where something links or spans between a river and a valley, serving as a connection between the two.
- F. None of above.
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_69f349937b648190a34ada70f6a2b534 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7817daf00819098936402e75ab0a6 |
completed | May 3, 2026, 5:10 p.m. |
| PD | Predicate disambiguation | batch_69f780fc5ed88190b7200ee5a29940af |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 1, 2026, 1:47 a.m.