Triple
T9561381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karkheh River |
E230681
|
entity |
| Predicate | hasDamFunction |
P89797
|
FINISHED |
| Object | flood control |
—
|
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: flood control | Statement: [Karkheh River, hasDamFunction, flood control]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDamFunction Context triple: [Karkheh River, hasDamFunction, flood control]
-
A.
hasDam
Indicates that a watercourse, reservoir, or similar feature is impounded or controlled by a specific dam.
-
B.
hadFunction
Indicates that an entity previously served or fulfilled a particular role, purpose, or function.
-
C.
isMajorDamOf
Indicates that one dam is the primary or most significant dam associated with a particular river, reservoir, or water system.
-
D.
hasDistributionFunction
Indicates that an entity is associated with a specific distribution function that characterizes how its values or occurrences are probabilistically or statistically distributed.
-
E.
typeOfDam
Indicates the specific kind or classification of a dam associated with an entity.
- F. None of above. chosen
Provenance (4 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_69ca847e53a88190a60eed7e02257f10 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd994d31e08190b139f5ad10d8ea31 |
completed | April 1, 2026, 10:16 p.m. |
| PD | Predicate disambiguation | batch_69ccd594d0ac8190a81bc11a3a538167 |
completed | April 1, 2026, 8:21 a.m. |
| PDg | Predicate description generation | batch_69ccd93e90048190a2b0d7c5c195ba98 |
completed | April 1, 2026, 8:37 a.m. |
Created at: March 30, 2026, 8:03 p.m.