Triple
T31357710
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dire Dawa |
E799780
|
entity |
| Predicate | hasNearbyWatershed |
P58176
|
FINISHED |
| Object | Awash River watershed |
—
|
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: Awash River watershed | Statement: [Dire Dawa, hasNearbyWatershed, Awash River watershed]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyWatershed Context triple: [Dire Dawa, hasNearbyWatershed, Awash River watershed]
-
A.
hasWatershed
Indicates that one geographic area or feature is part of, drains into, or is hydrologically defined by a particular watershed.
-
B.
hasWatershedWith
chosen
Indicates that two geographic areas share or are associated with the same watershed or drainage basin.
-
C.
hasNearbyWater
Indicates that one entity is located close to a body of water associated with or relevant to another entity.
-
D.
hasNearbyWaterBoard
Indicates that an entity is located close to, or within the jurisdictional area of, a water management or water regulatory board.
-
E.
hasNearbyWatersUsedBy
Indicates that a body of water located near an entity is utilized or accessed by another specified entity.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fee691952c8190822da83e46311d1d |
completed | May 9, 2026, 7:47 a.m. |
| PD | Predicate disambiguation | batch_69fee62f285c8190a625562a9b80526e |
completed | May 9, 2026, 7:45 a.m. |
Created at: April 29, 2026, 9:17 p.m.