Triple
T6218392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Selk'nam |
E139048
|
entity |
| Predicate | subsistenceMode |
P5381
|
FINISHED |
| Object | hunter-gatherer |
—
|
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: hunter-gatherer | Statement: [Selk'nam, subsistenceMode, hunter-gatherer]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsistenceMode Context triple: [Selk'nam, subsistenceMode, hunter-gatherer]
-
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.
agriculturalDependence
Indicates that one entity relies on another for agricultural resources, production, or support.
-
C.
livelihood
Indicates that one entity serves as the primary means of support, income, or subsistence for another entity.
-
D.
traditionalLifestyle
Indicates that an entity follows or maintains long-established customs, practices, and ways of living, typically in contrast to modern or industrialized lifestyles.
-
E.
nutritionMode
Indicates the way an entity obtains or processes nutrients for sustenance or growth.
- 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_69c008aecb0c81909984b48f733ce8ae |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062a481908190a1418d9fcfaf8137 |
completed | March 22, 2026, 9:44 p.m. |
| PD | Predicate disambiguation | batch_69c055fdea3c81908f5d910f0d36234a |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:21 p.m.