Triple
T4426779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cuyahoga River |
E95227
|
entity |
| Predicate | hasMeanderingCourse |
P55931
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Cuyahoga River, hasMeanderingCourse, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMeanderingCourse Context triple: [Cuyahoga River, hasMeanderingCourse, yes]
-
A.
hasWatercourseType
Indicates the specific kind or category of watercourse (such as river, stream, or canal) associated with an entity.
-
B.
hasTowpath
Indicates that a waterway or canal is accompanied by a path running alongside it, typically used for towing boats.
-
C.
hasRiver
Indicates that a location or area contains, is traversed by, or is directly associated with a river.
-
D.
followsWatercourse
Indicates that one entity runs alongside or traces the path of a watercourse such as a river, stream, or canal.
-
E.
hasBranchCanals
Indicates that an entity possesses or is connected to one or more subsidiary or secondary canals branching off from a main canal.
- 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_69b3453c2a0c8190926b574c90766db9 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3554fb28081909018eaecc0c5c230 |
completed | March 13, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69b34f5eabe88190a12b244ea71e46d6 |
completed | March 12, 2026, 11:42 p.m. |
| PDg | Predicate description generation | batch_69b3505a87b4819083fbbd58870e520b |
completed | March 12, 2026, 11:46 p.m. |
Created at: March 12, 2026, 11:30 p.m.