Triple
T12310161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Niagara Rapids |
E293454
|
entity |
| Predicate | riverSectionType |
P14635
|
FINISHED |
| Object | lower rapids |
—
|
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: lower rapids | Statement: [Lower Niagara Rapids, riverSectionType, lower rapids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: riverSectionType Context triple: [Lower Niagara Rapids, riverSectionType, lower rapids]
-
A.
riverFeatureType
chosen
Indicates the specific kind or category of physical or functional feature associated with a river (e.g., source, mouth, tributary, channel segment).
-
B.
riverSystem
Indicates that one entity is a river system to which the other entity belongs or is a component (such as a tributary or segment).
-
C.
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.
-
D.
waterwayClass
Indicates the classification or type of a waterway based on its navigational, functional, or physical characteristics.
-
E.
watercourseFeature
Indicates that a feature is a physical characteristic or component associated with a watercourse (such as a river, stream, or canal).
- 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_69d6ab6a2b50819082f6aedd32ed608a |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f621570819091ee1db2609233ea |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec02c008190a56aae60a3d9eff6 |
completed | April 10, 2026, 6:17 p.m. |
Created at: April 8, 2026, 9:53 p.m.