Triple
T15962968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Haditha Dam |
E387106
|
entity |
| Predicate | hasReservoirSurfaceUse |
P40334
|
FINISHED |
| Object | fisheries |
—
|
LITERAL 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: fisheries | Statement: [Haditha Dam, hasReservoirSurfaceUse, fisheries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReservoirSurfaceUse Context triple: [Haditha Dam, hasReservoirSurfaceUse, fisheries]
-
A.
reservoirUse
chosen
Indicates the way a reservoir is utilized or the purpose for which its stored water is used.
-
B.
hasWatershedUse
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
-
C.
usesSurfaceWater
Indicates that one entity relies on or draws from surface water sources (such as rivers, lakes, or reservoirs) for its activities or needs.
-
D.
hasWaterUse
Indicates a relationship where one entity utilizes or consumes water for a particular purpose, process, or function.
-
E.
basinUse
Indicates that a basin is used for a particular purpose, activity, 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e173b3bf6c81909230170e833d7ce7 |
completed | April 16, 2026, 11:41 p.m. |
| PD | Predicate disambiguation | batch_69e142d6fb588190b4176eab4bbae774 |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.