Triple
T28932145
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Big Chino Wash |
E733815
|
entity |
| Predicate | contributesHeadwatersTo |
P154707
|
FINISHED |
| Object | Verde River |
—
|
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: Verde River | Statement: [Big Chino Wash, contributesHeadwatersTo, Verde River]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: contributesHeadwatersTo Context triple: [Big Chino Wash, contributesHeadwatersTo, Verde River]
-
A.
isHeadwaterTributaryOf
chosen
Indicates that one watercourse is a source or upstream tributary that feeds into another watercourse.
-
B.
hasHeadwatersOf
Indicates that a specified location or feature is the source or origin point of a particular river or watercourse.
-
C.
hasHeadwatersIn
Indicates that the source or origin of a river, stream, or similar watercourse is located within a specified geographic area or feature.
-
D.
isMajorWatercourseOf
Indicates that a watercourse is a primary or significant river or stream associated with, or flowing through, a particular geographic area or feature.
-
E.
isWatercourseOf
Indicates that a watercourse (such as a river or stream) flows through, belongs to, or is geographically associated with a particular area or feature.
- 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_69f05b0b49b08190b8994b339c7980f6 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: April 28, 2026, 8:29 a.m.