Triple
T17138124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gisk’aast (Killer Whale) |
E415891
|
entity |
| Predicate | hasRightOver |
P39434
|
FINISHED |
| Object | specific Nisga’a territories |
—
|
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: specific Nisga’a territories | Statement: [Gisk’aast (Killer Whale), hasRightOver, specific Nisga’a territories]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRightOver Context triple: [Gisk’aast (Killer Whale), hasRightOver, specific Nisga’a territories]
-
A.
hasRightsOver
chosen
Indicates that one entity possesses legal, moral, or formal entitlements or authority over another entity.
-
B.
hasRightsStatus
Indicates that an entity is associated with a particular legal or usage rights condition or status.
-
C.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another entity.
-
D.
hasAccessTo
Indicates that one entity is permitted to enter, use, or interact with another entity, resource, or location.
-
E.
hasAccessTowards
Indicates that one entity possesses the ability, permission, or means to reach, use, or interact with another entity or 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_69d886d15af4819092f92f8a129763e6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e3f2d1277881909325ffd2a7aa4873 |
completed | April 18, 2026, 9:08 p.m. |
| PD | Predicate disambiguation | batch_69e3830192ac819091344a9e5a36c8c9 |
completed | April 18, 2026, 1:11 p.m. |
Created at: April 10, 2026, 5:36 a.m.