Triple
T14870460
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Porcupine River region |
E349728
|
entity |
| Predicate | hasResourceUse |
P4199
|
FINISHED |
| Object | caribou harvesting |
—
|
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: caribou harvesting | Statement: [Porcupine River region, hasResourceUse, caribou harvesting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResourceUse Context triple: [Porcupine River region, hasResourceUse, caribou harvesting]
-
A.
usedResource
Indicates that an entity has utilized or consumed a particular resource in performing an action or achieving a result.
-
B.
hasResourceBase
Indicates that one entity possesses, is founded on, or derives from another entity serving as its fundamental resource or base.
-
C.
hasPresentUse
Indicates that an entity is currently being used or serving a particular function at the present time.
-
D.
hasResourcePotential
Indicates that an entity possesses the capacity or suitability to provide, generate, or support a particular resource in the future.
-
E.
hasMajorResource
chosen
Indicates that an entity possesses or is characterized by a primary or most significant resource.
- 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_69d822ee4f408190b6ac3b2fa434f0df |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69ded57967748190a7c05ebb74aacb7c |
completed | April 15, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69de8c1798c08190b433e9ad21e41a42 |
completed | April 14, 2026, 6:48 p.m. |
Created at: April 10, 2026, 1:55 a.m.