Triple
T4953886
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euripus Strait |
E111233
|
entity |
| Predicate | hasTidalReversalFrequency |
P1735
|
FINISHED |
| Object | multiple times per day |
—
|
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: multiple times per day | Statement: [Euripus Strait, hasTidalReversalFrequency, multiple times per day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalReversalFrequency Context triple: [Euripus Strait, hasTidalReversalFrequency, multiple times per day]
-
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
Indicates that one entity exhibits observable tidal features caused by gravitational interactions with another entity.
-
C.
isTidal
chosen
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
D.
hasMaximumTidalBoreHeight
Indicates that one entity has a specified greatest recorded or expected height of its tidal bore.
-
E.
hasTidalEnergyDeveloper
Indicates that an entity is associated with or employs a specific developer responsible for tidal energy projects or technologies.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd71b82dd88190adfb08c3b3191fe0 |
completed | March 20, 2026, 4:11 p.m. |
| PD | Predicate disambiguation | batch_69bd6c3aa1388190b3e0c8ee1ba1e4fa |
completed | March 20, 2026, 3:48 p.m. |
Created at: March 20, 2026, 1:31 p.m.