Triple
T22934741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Batad |
E569549
|
entity |
| Predicate | riceTerraceIrrigationSource |
P150307
|
FINISHED |
| Object | mountain springs |
—
|
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: mountain springs | Statement: [Batad, riceTerraceIrrigationSource, mountain springs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riceTerraceIrrigationSource Context triple: [Batad, riceTerraceIrrigationSource, mountain springs]
-
A.
typeOfIrrigation
Indicates the specific irrigation method or system used to supply water to a given area or crop.
-
B.
hasIrrigatedAgriculture
Indicates that an entity engages in or possesses agricultural activities that are supported or sustained by artificial irrigation systems.
-
C.
hasIrrigationValley
Indicates that a valley is equipped with or associated with an irrigation system or infrastructure.
-
D.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
E.
irrigationScheme
Indicates that one entity is part of, served by, or associated with a particular irrigation scheme or system for water distribution.
- 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_69e24590862c8190858f180ad302adab |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18134484c8190b7311606c17d058d |
completed | April 29, 2026, 3:55 a.m. |
| PD | Predicate disambiguation | batch_69ef3b882e708190b0eb0c87021c75b8 |
completed | April 27, 2026, 10:33 a.m. |
| PDg | Predicate description generation | batch_69ef538a115081908982597f79355840 |
completed | April 27, 2026, 12:16 p.m. |
Created at: April 17, 2026, 3:44 p.m.