Triple
T347931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colorado River Indian Tribes |
E6980
|
entity |
| Predicate | hasLandBase |
P7001
|
FINISHED |
| Object | reservation land along the Colorado 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: reservation land along the Colorado River | Statement: [Colorado River Indian Tribes, hasLandBase, reservation land along the Colorado River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLandBase Context triple: [Colorado River Indian Tribes, hasLandBase, reservation land along the Colorado River]
-
A.
hasLandCoverage
Indicates that a specified area or region is covered or occupied by a particular type of land surface or land use.
-
B.
hasLandform
Indicates that one entity possesses, contains, or is characterized by a particular natural landform.
-
C.
usesOnLand
Indicates that one entity employs or operates another entity specifically in a land-based context.
-
D.
hasSoil
Indicates that one entity possesses, contains, or is associated with a particular type or instance of soil.
-
E.
hasGrounds
chosen
Indicates that one entity possesses or includes a physical area of land or outdoor space associated with it.
- 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_69a2e7951ba08190960e90823b5078f3 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2eb1c1c908190b3a01de893207ed1 |
completed | Feb. 28, 2026, 1:18 p.m. |
| PD | Predicate disambiguation | batch_69a2e95451a4819090f4e4fb9b21a493 |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.