Triple
T22641167
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavineño people |
E558828
|
entity |
| Predicate | usesForestFor |
P128550
|
FINISHED |
| Object | food gathering |
—
|
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: food gathering | Statement: [Cavineño people, usesForestFor, food gathering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesForestFor Context triple: [Cavineño people, usesForestFor, food gathering]
-
A.
isForested
Indicates that an area or region is covered predominantly by forest or dense tree vegetation.
-
B.
locatedInForest
Indicates that an entity is situated within the boundaries of a forest.
-
C.
hasForestType
Indicates that an area or location is characterized by a specific type or classification of forest.
-
D.
hasForestAssociation
chosen
Indicates an ecological or contextual relationship in which an entity is associated with, influenced by, or characteristically occurs in forest environments.
-
E.
treeUse
Indicates the way in which a tree is utilized or purposed within a given context.
- 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_69e24547f7fc819086e2c4ba3b979657 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f170116fe881908178cffef26e3ae7 |
completed | April 29, 2026, 2:42 a.m. |
| PD | Predicate disambiguation | batch_69ee6294c4c08190b7e4829f4b9af24b |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:04 p.m.