Triple
T19578757
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moffat Tunnel |
E489928
|
entity |
| Predicate | carriesWaterFrom |
P65384
|
FINISHED |
| Object | Western Slope of Colorado |
—
|
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: Western Slope of Colorado | Statement: [Moffat Tunnel, carriesWaterFrom, Western Slope of Colorado]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carriesWaterFrom Context triple: [Moffat Tunnel, carriesWaterFrom, Western Slope of Colorado]
-
A.
transportsWaterFrom
chosen
Indicates that one entity carries or conveys water from a specified source entity to another location or entity.
-
B.
transportsWaterTo
Indicates that one entity carries or conveys water from its location or source to another entity or destination.
-
C.
managesWaterFrom
Indicates that one entity is responsible for controlling, directing, or handling water originating from another entity.
-
D.
carriedWaterMostly
Indicates that one entity was primarily responsible for transporting or conveying water for another entity or purpose.
-
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_69d8e8dd9374819098e36349b3211663 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6402693d88190a828c0e136895783 |
completed | April 20, 2026, 3:03 p.m. |
| PD | Predicate disambiguation | batch_69e514dbdb988190b55931a8138c73e7 |
completed | April 19, 2026, 5:46 p.m. |
Created at: April 10, 2026, 1:42 p.m.