Triple

T15027191
Position Surface form Disambiguated ID Type / Status
Subject Yakama Nation E378247 entity
Predicate hasTreatyRight P116439 FINISHED
Object fishing rights on the Columbia River 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 on the Columbia River | Statement: [Yakama Nation, hasTreatyRight, fishing rights on the Columbia River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTreatyRight
Context triple: [Yakama Nation, hasTreatyRight, fishing rights on the Columbia River]
  • A. hasMainTreaty
    Indicates that one entity is the primary or principal treaty associated with another entity.
  • B. treatyPower
    Indicates that one entity holds the authority or capacity to negotiate, conclude, or be bound by treaties with another entity.
  • C. establishedByTreatyOrAct
    Indicates that the relationship or entity was formally created, defined, or authorized through a specific treaty or legislative act.
  • D. hasSovereignRightsHolder
    Indicates that one entity holds the sovereign rights or ultimate legal authority over another entity, such as a territory, resource, or jurisdiction.
  • E. hasNoSingleTreaty
    Indicates that there is no single, unified treaty governing the relationship between the entities, implying multiple or fragmented agreements instead.
  • F. None of above. chosen

Provenance (4 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_69d85cd46b2c819090d054c27787f677 completed April 10, 2026, 2:13 a.m.
NER Named-entity recognition batch_69ded7dfcb508190aec8cd667e27a8ea completed April 15, 2026, 12:12 a.m.
PD Predicate disambiguation batch_69de9a67cbc481909c19c2de57de4eb7 completed April 14, 2026, 7:50 p.m.
PDg Predicate description generation batch_69deb1a88d588190996afa8e5b32b552 completed April 14, 2026, 9:29 p.m.
Created at: April 10, 2026, 2:58 a.m.