Triple
T26266077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tahltan people |
E656985
|
entity |
| Predicate | hasResourceIssues |
P114170
|
FINISHED |
| Object | mining development in Tahltan territory |
—
|
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: mining development in Tahltan territory | Statement: [Tahltan people, hasResourceIssues, mining development in Tahltan territory]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResourceIssues Context triple: [Tahltan people, hasResourceIssues, mining development in Tahltan territory]
-
A.
hasIssueWith
chosen
Indicates that one entity experiences a problem, conflict, or concern related to another entity.
-
B.
hasOngoingIssues
Indicates that an entity is currently experiencing unresolved or continuing problems or difficulties.
-
C.
hasLocalIssues
Indicates that an entity is associated with or affected by specific issues or problems occurring within a particular local area or community.
-
D.
hasNoIssue
Indicates that there are no problems, defects, or conflicts associated with the referenced entity or situation.
-
E.
hasAccessIssues
Indicates that an entity experiences problems, limitations, or failures when attempting to access another entity, resource, or service.
- 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_69ee5b4e21bc819082be98bc9ab09796 |
completed | April 26, 2026, 6:37 p.m. |
| NER | Named-entity recognition | batch_69fd7e364a648190a1e9e1d9fc76e99e |
completed | May 8, 2026, 6:09 a.m. |
| PD | Predicate disambiguation | batch_69fd7bb547608190a3b04dddbca6b8bc |
completed | May 8, 2026, 5:59 a.m. |
Created at: April 26, 2026, 9:11 p.m.