Triple
T36698634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pueblo Secoya |
E906157
|
entity |
| Predicate | relaciónConLaNaturaleza |
P137171
|
FINISHED |
| Object | manejo tradicional de bosques y ríos |
—
|
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: manejo tradicional de bosques y ríos | Statement: [pueblo Secoya, relaciónConLaNaturaleza, manejo tradicional de bosques y ríos]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relaciónConLaNaturaleza Context triple: [pueblo Secoya, relaciónConLaNaturaleza, manejo tradicional de bosques y ríos]
-
A.
relatesToNatureOf
chosen
Indicates a general relationship that concerns or characterizes the inherent nature, essence, or fundamental qualities of something.
-
B.
territorialNature
Indicates a tendency of an entity to defend or assert control over a specific area or domain against others.
-
C.
viewOnNature
Indicates a person's general attitude, perspective, or philosophy regarding nature and the natural environment.
-
D.
sharesNatureWith
Indicates that two entities possess the same fundamental characteristics, qualities, or essence.
-
E.
benefitNature
Indicates that one entity provides an advantage, positive impact, or beneficial effect to another entity.
- 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_69fb2e940d5c8190bceae77daf4ef512 |
completed | May 6, 2026, 12:05 p.m. |
| PD | Predicate disambiguation | batch_69f9fec70bd881909c658a3c5020318b |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:12 p.m.