Triple
T8683147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tsalka |
E206086
|
entity |
| Predicate | waterBodyUsedFor |
P44236
|
FINISHED |
| Object | Tsalka Reservoir used for irrigation |
—
|
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: Tsalka Reservoir used for irrigation | Statement: [Tsalka, waterBodyUsedFor, Tsalka Reservoir used for irrigation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterBodyUsedFor Context triple: [Tsalka, waterBodyUsedFor, Tsalka Reservoir used for irrigation]
-
A.
waterbodyUsedFor
chosen
Indicates that a particular water body is utilized for a specific purpose, activity, or function.
-
B.
bodyOfWater
Indicates that one entity is a body of water that is geographically or physically associated with another entity.
-
C.
waterbodyID
Indicates a unique identifier that links an entity to a specific body of water.
-
D.
appliesToWaterBody
Indicates that something (such as a rule, condition, property, or effect) is relevant or applicable specifically to a particular water body.
-
E.
waterbodyType
Indicates the classification of a water body according to its type (e.g., river, lake, ocean, etc.).
- 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_69ca835379688190aa06b9d98e684d58 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc4ae9da3c8190866e24970a7aeba3 |
completed | March 31, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69cc4567b5c881908d9ec5dcfc783fac |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:32 p.m.