Triple
T30772770
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parsabad |
E783570
|
entity |
| Predicate | usesRiverForIrrigation |
P121141
|
FINISHED |
| Object | Aras River |
—
|
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: Aras River | Statement: [Parsabad, usesRiverForIrrigation, Aras River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesRiverForIrrigation Context triple: [Parsabad, usesRiverForIrrigation, Aras River]
-
A.
usedForIrrigationIn
Indicates that something serves as a means or resource for irrigating land or crops in a specified location or context.
-
B.
hasRiverUse
chosen
Indicates that one entity makes use of a river associated with another entity, such as for transport, irrigation, recreation, or other purposes.
-
C.
usedIrrigation
Indicates that an entity applied or employed an irrigation system or method to supply water to land or crops.
-
D.
nowIrrigatedBy
Indicates that an area or land parcel is currently being supplied with water through a specified irrigation source or system.
-
E.
hasIrrigationValley
Indicates that a valley is equipped with or associated with an irrigation system or infrastructure.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6df450014819099d118e5c2d697fa |
completed | May 3, 2026, 5:38 a.m. |
| PD | Predicate disambiguation | batch_69f6de07836481908785cde9c511920b |
completed | May 3, 2026, 5:32 a.m. |
Created at: April 29, 2026, 8:40 p.m.