Triple
T5552694
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Recuay culture |
E145562
|
entity |
| Predicate | usedIrrigation |
P65328
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Recuay culture, usedIrrigation, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedIrrigation Context triple: [Recuay culture, usedIrrigation, yes]
-
A.
usedIrrigationFrom
Indicates that one entity applied or relied on irrigation resources, systems, or methods originating from another entity.
-
B.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
C.
irrigates
Indicates that one entity supplies water to another, typically land or crops, for the purpose of supporting growth or maintaining moisture.
-
D.
hasIrrigationArea
Indicates that an entity possesses or is associated with a specific area of land equipped or designated for irrigation.
-
E.
waterUse
Indicates the amount or manner in which water is consumed, utilized, or withdrawn by an entity or activity.
- 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_69c008fb879c81909f5bfa56fadc1d46 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01ff872bc81908e14776f7ba4154e |
completed | March 22, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69c01b0e72f08190bf705d8fe1639401 |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f051e508190b3886d87b4afdd0b |
completed | March 22, 2026, 4:55 p.m. |
Created at: March 22, 2026, 3:35 p.m.