Triple
T6108913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joggins Fossil Cliffs |
E136181
|
entity |
| Predicate | tideRange |
P4652
|
FINISHED |
| Object | large tidal range of the Bay of Fundy |
—
|
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: large tidal range of the Bay of Fundy | Statement: [Joggins Fossil Cliffs, tideRange, large tidal range of the Bay of Fundy]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tideRange Context triple: [Joggins Fossil Cliffs, tideRange, large tidal range of the Bay of Fundy]
-
A.
hasTidalRange
chosen
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
B.
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.
-
C.
stormSurgeHeight_feet
Indicates the height of the storm surge, measured in feet, typically above a defined reference level such as normal tide.
-
D.
waterLevelRise
Indicates that the level of water in a given area or container has increased over time.
-
E.
maximumTsunamiHeight
Indicates the greatest recorded or expected vertical height reached by a tsunami at a given location or event.
- 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_69c0089ea6f88190b349be53e04b4f5f |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b835ed48190971c3ba397ca329f |
completed | March 22, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69c049f80e2081909b7d84a104cda68d |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:13 p.m.