Triple
T26779200
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cherry Creek Trail |
E670200
|
entity |
| Predicate | waterwayFollowed |
P168928
|
FINISHED |
| Object | Cherry Creek |
—
|
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: Cherry Creek | Statement: [Cherry Creek Trail, waterwayFollowed, Cherry Creek]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waterwayFollowed Context triple: [Cherry Creek Trail, waterwayFollowed, Cherry Creek]
-
A.
waterwayThrough
Indicates that a waterway (such as a river or canal) passes through or traverses a specified geographic area or feature.
-
B.
waterwayServed
Indicates that a place, facility, or infrastructure is served by, connected to, or functionally supported by a particular waterway.
-
C.
usesWaterwaysFor
Indicates that one entity relies on or employs waterways as a means or route to perform an activity or function in relation to another entity.
-
D.
usedWaterway
Indicates that one entity traveled, transported goods, or otherwise moved via a particular waterway as the route or medium of use.
-
E.
waterbodyOnCourse
Indicates that a waterbody lies along, intersects, or is situated on the path of a particular course, such as a river or stream.
- F. None of above. chosen
Provenance (4 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_69eeb31c925881909b597f6e40056d28 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 27, 2026, 4:07 a.m.