Triple
T14998724
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chagga people |
E374025
|
entity |
| Predicate | traditionalIrrigationSystem |
P79075
|
FINISHED |
| Object | mfongo furrow system |
—
|
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: mfongo furrow system | Statement: [Chagga people, traditionalIrrigationSystem, mfongo furrow system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalIrrigationSystem Context triple: [Chagga people, traditionalIrrigationSystem, mfongo furrow system]
-
A.
typeOfIrrigation
chosen
Indicates the specific irrigation method or system used to supply water to a given area or crop.
-
B.
usedIrrigation
Indicates that an entity applied or employed an irrigation system or method to supply water to land or crops.
-
C.
hasIrrigation
Indicates that an entity is equipped with or benefits from an irrigation system supplying water.
-
D.
usedIrrigationFrom
Indicates that one entity applied or relied on irrigation resources, systems, or methods originating from another entity.
-
E.
hasIrrigationDependence
Indicates that one entity relies on another entity or system to provide irrigation for its water needs.
- 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_69d85ccc84388190aa151e5173370c8d |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded71a5618819083ae96a79735ef98 |
completed | April 15, 2026, 12:08 a.m. |
| PD | Predicate disambiguation | batch_69de9a6169b48190a679609febd2d0e3 |
completed | April 14, 2026, 7:49 p.m. |
Created at: April 10, 2026, 2:54 a.m.