Triple

T5744181
Position Surface form Disambiguated ID Type / Status
Subject Snuneymuxw First Nation E126686 entity
Predicate hasTreatyProcessStatus P54899 FINISHED
Object engaged in British Columbia treaty process 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: engaged in British Columbia treaty process | Statement: [Snuneymuxw First Nation, hasTreatyProcessStatus, engaged in British Columbia treaty process]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasTreatyProcessStatus
Context triple: [Snuneymuxw First Nation, hasTreatyProcessStatus, engaged in British Columbia treaty process]
  • A. treatyStatus
    Indicates the current legal or diplomatic condition of a treaty between parties, such as whether it is proposed, signed, ratified, active, suspended, or terminated.
  • B. treatyProcess chosen
    Indicates a formal process of negotiating, drafting, adopting, or implementing a treaty between parties.
  • C. hasMainTreaty
    Indicates that one entity is the primary or principal treaty associated with another entity.
  • D. treatyConcluded
    Indicates that a formal agreement or treaty has been officially finalized and brought into force between the involved parties.
  • 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.

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_69c0083179548190b384b0bf3c08ca4d completed March 22, 2026, 3:18 p.m.
NER Named-entity recognition batch_69c02b52663c8190ab44258468d4296d completed March 22, 2026, 5:48 p.m.
PD Predicate disambiguation batch_69c021ca61688190875bd6107161c284 completed March 22, 2026, 5:07 p.m.
Created at: March 22, 2026, 3:48 p.m.