Triple
T5688438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bay of Fundy |
E125368
|
entity |
| Predicate | hasTidalPhenomenon |
P57287
|
FINISHED |
| Object | tidal bore |
—
|
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: tidal bore | Statement: [Bay of Fundy, hasTidalPhenomenon, tidal bore]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalPhenomenon Context triple: [Bay of Fundy, hasTidalPhenomenon, tidal bore]
-
A.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
B.
containsTidalFeatures
chosen
Indicates that one entity exhibits observable tidal features caused by gravitational interactions with another entity.
-
C.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
D.
isTidallyLockedTo
Indicates that one object's rotational period matches its orbital period around another object, so the same side always faces that other object.
-
E.
isTidallyLockedWith
Indicates that two astronomical bodies always show the same face to each other because one’s rotation period matches its orbital period around the other.
- 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_69c0082a884c8190a79001bae658941f |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c029014588819094a2a0f6f9b66bab |
completed | March 22, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c021c0e0408190ab6c3cd3f907e80f |
completed | March 22, 2026, 5:07 p.m. |
Created at: March 22, 2026, 3:44 p.m.