Triple

T28983550
Position Surface form Disambiguated ID Type / Status
Subject Eastern Snake River Plain Aquifer E734614 entity
Predicate hasUseConflict P34137 FINISHED
Object surface water users on Snake 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: surface water users on Snake River | Statement: [Eastern Snake River Plain Aquifer, hasUseConflict, surface water users on Snake River]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasUseConflict
Context triple: [Eastern Snake River Plain Aquifer, hasUseConflict, surface water users on Snake River]
  • A. conflictUse chosen
    Indicates a relationship where one entity’s use, application, or operation is incompatible with, obstructs, or negatively interferes with another entity’s use.
  • B. hasConflictStatus
    Indicates that there exists a state of conflict or dispute associated with the relationship between the involved entities.
  • C. hasConflictCause
    Indicates that one entity is the cause or source of a conflict involving another entity.
  • D. hasRelatedConflict
    Indicates that one entity is associated with another entity through a related or connected conflict, dispute, or incompatibility.
  • E. hasOngoingConflict
    Indicates that there is a current, unresolved state of opposition, dispute, or hostilities between the related entities.
  • 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_69f05b0dd9b481908b7901e1c95ff6b2 completed April 28, 2026, 7 a.m.
NER Named-entity recognition batch_69f6691f5e188190b12c7b2eb729a45e completed May 2, 2026, 9:14 p.m.
PD Predicate disambiguation batch_69f6659b62fc8190b21555d0ba54db2d completed May 2, 2026, 8:59 p.m.
Created at: April 28, 2026, 9:12 a.m.