Triple
T5785027
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pemon |
E128248
|
entity |
| Predicate | usesAgriculturalTechnique |
P4104
|
FINISHED |
| Object | slash-and-burn 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: slash-and-burn agriculture | Statement: [Pemon, usesAgriculturalTechnique, slash-and-burn agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesAgriculturalTechnique Context triple: [Pemon, usesAgriculturalTechnique, slash-and-burn agriculture]
-
A.
usedAgriculture
Indicates that an entity employed agricultural methods, practices, or resources for cultivation, production, or related purposes.
-
B.
agriculturalPractice
chosen
Indicates a relationship where an entity engages in, applies, or is associated with a specific method or technique of agriculture or farming.
-
C.
agricultureUse
Indicates that something is used for, involved in, or designated for agricultural activities or purposes.
-
D.
hasAgriculturalCharacter
Indicates that something possesses qualities, features, or uses typical of agriculture or farming activities.
-
E.
isCultivatedAs
Indicates that one entity is intentionally grown, tended, or produced by another as a crop, resource, or cultivated organism.
- 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_69c0084450048190bc647b649a05136b |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02a1af0ec8190a47be1b7e7b5cda7 |
completed | March 22, 2026, 5:42 p.m. |
| PD | Predicate disambiguation | batch_69c021d2cd608190b98a7e3aa7001d27 |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:51 p.m.