Triple
T27273584
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Achagua people |
E688123
|
entity |
| Predicate | traditionalHunting |
P5381
|
FINISHED |
| Object | small game hunting |
—
|
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: small game hunting | Statement: [Achagua people, traditionalHunting, small game hunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalHunting Context triple: [Achagua people, traditionalHunting, small game hunting]
-
A.
hunting
Indicates one entity actively pursuing and attempting to capture or kill another entity, typically as prey.
-
B.
huntingStyle
Indicates the characteristic manner or method an entity typically uses when hunting.
-
C.
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.
-
D.
huntingTime
Indicates the time period during which a hunting activity takes place or is scheduled.
-
E.
associatedWithHunting
Indicates a relationship where an entity is connected to, involved in, or commonly linked with the activity or practice of hunting.
- 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_69ef3558cf8881909595ef89daf6e14a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: April 27, 2026, 11:01 a.m.