Triple
T22641191
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cavineño people |
E558828
|
entity |
| Predicate | usesFishingTechnique |
P87869
|
FINISHED |
| Object | nets |
—
|
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: nets | Statement: [Cavineño people, usesFishingTechnique, nets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFishingTechnique Context triple: [Cavineño people, usesFishingTechnique, nets]
-
A.
fishingUse
chosen
Indicates that one entity uses another as a tool, method, or context specifically for the activity of fishing.
-
B.
fishingType
Indicates the specific method or style of fishing associated with an activity, event, or location.
-
C.
traditionalFishingMethod
Indicates a relationship where a fishing activity is carried out using long-established, customary techniques passed down through local or ancestral practice.
-
D.
fishingActivity
Indicates an activity where an entity engages in catching or attempting to catch fish or other aquatic organisms.
-
E.
fishedFor
Indicates that one entity attempted to catch another entity (typically an animal or resource) by engaging in fishing activities.
- 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.