Triple
T23751092
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Port Gamble S’Klallam Tribe |
E586968
|
entity |
| Predicate | hasTreatyRights |
P116439
|
FINISHED |
| Object | fishing rights |
—
|
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: fishing rights | Statement: [Port Gamble S’Klallam Tribe, hasTreatyRights, fishing rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTreatyRights Context triple: [Port Gamble S’Klallam Tribe, hasTreatyRights, fishing rights]
-
A.
hasTreatyRight
chosen
Indicates that an entity holds a legally recognized right or entitlement established by a formal treaty with another party.
-
B.
treatyRights
Indicates that there exist rights, obligations, or privileges established by a formal treaty between parties.
-
C.
hasSovereignRightsHolder
Indicates that one entity holds the sovereign rights or ultimate legal authority over another entity, such as a territory, resource, or jurisdiction.
-
D.
hasIndigenousRightsClaims
Indicates that an entity asserts or is recognized as having legal or customary rights claims based on its status as an Indigenous people or community.
-
E.
hasMainTreaty
Indicates that one entity is the primary or principal treaty associated with 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_69e2490a0eec81908cdef8a862828d7a |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bcc1d4e8819099d3b4136f28f0c6 |
completed | April 29, 2026, 8:09 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
Created at: April 17, 2026, 7:13 p.m.