Triple
T36773691
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Boyer River |
E908549
|
entity |
| Predicate | hasMajorLandUseInBasin |
P38195
|
FINISHED |
| Object | row-crop agriculture |
—
|
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: row-crop agriculture | Statement: [Boyer River, hasMajorLandUseInBasin, row-crop agriculture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorLandUseInBasin Context triple: [Boyer River, hasMajorLandUseInBasin, row-crop agriculture]
-
A.
drainageBasinLandUse
Indicates how the land within a drainage basin is utilized or managed (e.g., for agriculture, urban development, or natural vegetation).
-
B.
hasWatershedUse
Indicates that a particular type of use, activity, or function is associated with or applied to a watershed.
-
C.
basinUse
Indicates that a basin is used for a particular purpose, activity, or function.
-
D.
majorLandUse
chosen
Indicates the primary way a given area of land is utilized or designated (e.g., residential, commercial, agricultural).
-
E.
hasFloodplainUse
Indicates that a floodplain area is being used or designated for a particular purpose or activity.
- 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_69f76e798aa08190ace31098d1b13e9f |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a0352b6c7dc81908f190060eb1e1857 |
completed | May 12, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_6a03507c37d4819091068b2ec5cacef9 |
completed | May 12, 2026, 4:08 p.m. |
Created at: May 3, 2026, 4:12 p.m.