Triple
T22986314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jordan and Syria |
E571615
|
entity |
| Predicate | waterTension |
P150503
|
FINISHED |
| Object | disputes over Yarmouk River usage |
—
|
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: disputes over Yarmouk River usage | Statement: [Jordan and Syria, waterTension, disputes over Yarmouk River usage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterTension Context triple: [Jordan and Syria, waterTension, disputes over Yarmouk River usage]
-
A.
waterFilled
Indicates that one entity is filled or occupied with water, typically to a certain level or capacity.
-
B.
waterVolume
Indicates the amount of water present in or associated with an entity, typically measured as a volume.
-
C.
waterLevelTrend
Indicates the direction and rate at which a body of water’s level is changing over time (e.g., rising, falling, or stable).
-
D.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
E.
waterColumnZone
Indicates the specific vertical region or layer within a body of water where an entity or process is located or occurs.
- 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_69e245b3c50481908bb3741ec9f40862 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f182996ee08190ab74014ee7ecac2b |
completed | April 29, 2026, 4:01 a.m. |
| PD | Predicate disambiguation | batch_69ef3b974e7c8190b8be11dbb4518693 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538b29c081908fa56ee35a1dcee7 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:49 p.m.