Triple
T36698617
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pueblo Secoya |
E906157
|
entity |
| Predicate | medioDeSubsistencia |
P5381
|
FINISHED |
| Object | caza |
—
|
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: caza | Statement: [pueblo Secoya, medioDeSubsistencia, caza]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: medioDeSubsistencia Context triple: [pueblo Secoya, medioDeSubsistencia, caza]
-
A.
traditionalSubsistence
chosen
Indicates that an entity relies on customary, small-scale methods of obtaining food and resources (such as hunting, gathering, fishing, or small-scale farming) primarily for direct consumption rather than for market sale.
-
B.
subsistenceEnvironment
Indicates the type of environment or setting in which an entity’s basic living or survival activities are carried out.
-
C.
hasSubsistence
Indicates that one entity provides or serves as the means of basic support, livelihood, or survival for another entity.
-
D.
secondaryFood
Indicates that one entity serves as a secondary or supplementary food source in relation to another entity.
-
E.
agriculturalDependence
Indicates that one entity relies on another for agricultural resources, production, or support.
- 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.