Triple
T31348817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orma people |
E799526
|
entity |
| Predicate | usesRiverineAreasOf |
P162290
|
FINISHED |
| Object | Tana 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: Tana River | Statement: [Orma people, usesRiverineAreasOf, Tana River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRiverineAreasOf Context triple: [Orma people, usesRiverineAreasOf, Tana River]
-
A.
locatedInRiverArea
Indicates that one entity is situated within the geographic area occupied by, adjacent to, or directly associated with a particular river.
-
B.
riverineLocation
Indicates that something is located in, along, or directly associated with a river or river system.
-
C.
hasRiparianZone
Indicates that an area is adjacent to and ecologically influenced by a body of water, forming its riparian (riverbank or shoreline) zone.
-
D.
isCoastalOrRiverine
Indicates that a place is located along a sea coast or adjacent to a river, reflecting a shoreline or riverbank relationship.
-
E.
useRiverSystems
chosen
Indicates that an entity utilizes or manages river systems for a particular purpose or function.
- 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_69f224e51614819083141459a080e97c |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 29, 2026, 9:17 p.m.