Triple
T28290297
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Basin |
E713405
|
entity |
| Predicate | hasLegalAllocationType |
P77513
|
FINISHED |
| Object | apportioned water rights |
—
|
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: apportioned water rights | Statement: [Lower Basin, hasLegalAllocationType, apportioned water rights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalAllocationType Context triple: [Lower Basin, hasLegalAllocationType, apportioned water rights]
-
A.
hasLegalThresholdType
Indicates that something is associated with a specific type or category of legal threshold that applies to it.
-
B.
hasLegalRole
Indicates that an entity holds a specific legal capacity, status, or function in relation to another entity or context.
-
C.
hasLegalSystemType
Indicates that an entity possesses or is governed by a particular type or form of legal system.
-
D.
allocationType
chosen
Indicates the specific manner or category by which resources, responsibilities, or items are assigned or distributed among entities.
-
E.
hasLegalRight
Indicates that an entity possesses an officially recognized legal entitlement or permission to perform an action or hold a claim regarding another 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_69efb52371d88190a1381c4e58a3b731 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 27, 2026, 11:29 p.m.