Triple

T28078585
Position Surface form Disambiguated ID Type / Status
Subject Upper Basin E709614 entity
Predicate definedByAgreement P145119 FINISHED
Object Colorado River Compact of 1922 NE NERFINISHED

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: Colorado River Compact of 1922 | Statement: [Upper Basin, definedByAgreement, Colorado River Compact of 1922]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: definedByAgreement
Context triple: [Upper Basin, definedByAgreement, Colorado River Compact of 1922]
  • A. formedByAgreementWith chosen
    Indicates that something comes into existence or is established as a direct result of a formal agreement between parties.
  • B. basedOnAgreementWith
    Indicates that something exists, is done, or is determined on the basis of a prior agreement or accord between the involved parties.
  • C. implementsAgreementWith
    Indicates that one party carries out or fulfills the terms of an agreement made with another party.
  • D. involvedAgreement
    Indicates that an entity participates in, is a party to, or is otherwise associated with a specific agreement or contract.
  • E. requiresAgreementWith
    Indicates that one entity’s action, decision, or validity is contingent upon obtaining consent or formal agreement from another specified 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_69ef9b7037f0819095bb90eaccbcaf32 completed April 27, 2026, 5:22 p.m.
NER Named-entity recognition batch_69f7688dd3d08190ad13d0e780570a1c completed May 3, 2026, 3:23 p.m.
PD Predicate disambiguation batch_69f767fcf2f881908bacc7bfc38e68a5 completed May 3, 2026, 3:21 p.m.
Created at: April 27, 2026, 8:50 p.m.