Triple
T36698621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pueblo Secoya |
E906157
|
entity |
| Predicate | usoDePlantas |
P51056
|
FINISHED |
| Object | uso de plantas medicinales amazónicas |
—
|
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: uso de plantas medicinales amazónicas | Statement: [pueblo Secoya, usoDePlantas, uso de plantas medicinales amazónicas]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usoDePlantas Context triple: [pueblo Secoya, usoDePlantas, uso de plantas medicinales amazónicas]
-
A.
plantUse
chosen
Indicates that a plant is used for a particular purpose, function, or application.
-
B.
hostsPlantOf
Indicates that one entity serves as a host environment or substrate on which a particular plant lives, grows, or depends.
-
C.
involvesPlant
Indicates that the relationship or action includes or pertains to a plant as a participating entity.
-
D.
usedInPlant
Indicates that something is utilized or applied within a plant, such as in its processes, operations, or systems.
-
E.
isPlantOf
Indicates that one entity is a plant that belongs to, is associated with, or is characteristic of another entity (such as a region, habitat, or owner).
- 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_69f76e7195c48190b5580c9cfb01e95f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7c7ebdea48190b0e7565e4e09ec9e |
completed | May 3, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69f7c4796ebc819084a0dc08505e5f14 |
completed | May 3, 2026, 9:56 p.m. |
Created at: May 3, 2026, 4:12 p.m.