Triple
T26199592
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mru people |
E655193
|
entity |
| Predicate | typeOfAgriculture |
P114419
|
FINISHED |
| Object | rain-fed agriculture |
—
|
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: rain-fed agriculture | Statement: [Mru people, typeOfAgriculture, rain-fed agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfAgriculture Context triple: [Mru people, typeOfAgriculture, rain-fed agriculture]
-
A.
hasAgriculturalType
Indicates that an entity is associated with or classified by a specific type or category of agriculture.
-
B.
agriculturalPractice
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
-
C.
cultivationType
chosen
Indicates the method or system by which something (typically crops or land) is cultivated or farmed.
-
D.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
E.
agriculturalFocus
Indicates that an entity is primarily concerned with, oriented toward, or specializing in agriculture or farming-related activities.
- 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_69ee5b48236c81908fe385b6afc4f60b |
completed | April 26, 2026, 6:36 p.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: April 26, 2026, 8:47 p.m.