Triple
T15504507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reversing Falls Rapids |
E379045
|
entity |
| Predicate | atSlackTide |
P116424
|
FINISHED |
| Object | water level equalizes |
—
|
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: water level equalizes | Statement: [Reversing Falls Rapids, atSlackTide, water level equalizes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: atSlackTide Context triple: [Reversing Falls Rapids, atSlackTide, water level equalizes]
-
A.
tideType
Indicates the specific category or phase of the tide (such as high, low, rising, or falling) associated with a given tidal event or condition.
-
B.
stormSurgeHeightLocation
Indicates the height of a storm surge measured at or associated with a specific location.
-
C.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
D.
boreTideFrequency
Indicates how often a tidal bore occurs within a given time period.
-
E.
tidalCycle
chosen
Indicates the recurring pattern or phase of tides associated with an entity, such as its current position within a tidal rise-and-fall cycle.
- 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_69d85cd53a7c819080f5b9042c4c199e |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e03fcd5d948190b25a67a72ef980e9 |
completed | April 16, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69ded2896a9c8190a8b9627deb3c17b4 |
completed | April 14, 2026, 11:49 p.m. |
Created at: April 10, 2026, 3:54 a.m.