Triple
T14027432
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kake, Alaska |
E337496
|
entity |
| Predicate | subsistenceResources |
P20746
|
FINISHED |
| Object | salmon |
—
|
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: salmon | Statement: [Kake, Alaska, subsistenceResources, salmon]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subsistenceResources Context triple: [Kake, Alaska, subsistenceResources, salmon]
-
A.
traditionalSubsistence
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.
hasSubsistence
Indicates that one entity provides or serves as the means of basic support, livelihood, or survival for another entity.
-
C.
primaryFoodAcquisition
Indicates the main method or strategy by which an entity obtains its food or nutritional resources.
-
D.
naturalResources
Indicates that one entity possesses, contains, or is a source of natural resources for another entity.
-
E.
foodSources
chosen
Indicates a relationship where one entity serves as a source of food or nourishment for another entity.
- 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_69d81c6543a48190bd5ba93d7419e797 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2fa830ac81908cb7df7c9e81e42a |
completed | April 14, 2026, 12:14 p.m. |
| PD | Predicate disambiguation | batch_69de05ab36b48190920efb1869bdb1fe |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:20 p.m.