Triple
T22779261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tofa people |
E563787
|
entity |
| Predicate | minorSubsistenceActivity |
P5381
|
FINISHED |
| Object | fur 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: fur hunting | Statement: [Tofa people, minorSubsistenceActivity, fur hunting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: minorSubsistenceActivity Context triple: [Tofa people, minorSubsistenceActivity, fur hunting]
-
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.
pastoralActivities
Indicates activities related to providing spiritual care, guidance, or religious leadership within a community.
-
C.
hasSubsistence
Indicates that one entity provides or serves as the means of basic support, livelihood, or survival for another entity.
-
D.
secondaryActivity
Indicates that an entity engages in an additional, non-primary activity or role alongside its main activity.
-
E.
typicalActivity
Indicates that an entity is commonly or characteristically engaged in a particular activity.
- 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_69e24554497c819080b996e071de27c2 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17b63d348819085668e3d9ac78ffa |
completed | April 29, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69eed2c32e8c8190b73bb9965ed47d64 |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:28 p.m.