Triple

T20896692
Position Surface form Disambiguated ID Type / Status
Subject Prairie Provinces Water Board E514555 entity
Predicate typeOfAgreementFramework P38198 FINISHED
Object intergovernmental water management framework 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: intergovernmental water management framework | Statement: [Prairie Provinces Water Board, typeOfAgreementFramework, intergovernmental water management framework]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: typeOfAgreementFramework
Context triple: [Prairie Provinces Water Board, typeOfAgreementFramework, intergovernmental water management framework]
  • A. hasTypeOfAgreement chosen
    Indicates that one entity is associated with, or governed by, a specific category or type of agreement.
  • B. typeOfContract
    Indicates the specific kind or category of contractual agreement that applies between the related entities.
  • C. basedOnAgreementWith
    Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
  • D. aimOfAgreement
    Indicates the intended purpose or objective that an agreement is designed to achieve.
  • E. implementsAgreementWith
    Indicates that one party carries out or fulfills the terms of an agreement made with another party.
  • 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_69e0b4f7ebe48190952a85547a0f31a1 completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6d062f26c81908d99d6a9d3b99604 completed April 21, 2026, 1:18 a.m.
PD Predicate disambiguation batch_69e5c9ac91108190a6700fcdf2f11890 completed April 20, 2026, 6:37 a.m.
Created at: April 16, 2026, 12:47 p.m.