Triple
T15310678
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | North Sea tides |
E366027
|
entity |
| Predicate | hasTidalCycle |
P116424
|
FINISHED |
| Object | two high tides per lunar 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: two high tides per lunar day | Statement: [North Sea tides, hasTidalCycle, two high tides per lunar day]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTidalCycle Context triple: [North Sea tides, hasTidalCycle, two high tides per lunar day]
-
A.
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.
-
B.
hasTidalRange
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
-
C.
isTidallyLockedTo
Indicates that one object's rotational period matches its orbital period around another object, so the same side always faces that other object.
-
D.
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.
-
E.
containsTidalFeatures
Indicates that one entity exhibits observable tidal features caused by gravitational interactions with another entity.
- 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_69d85a113ee881908e297a1d38dd79fa |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03cd176708190b0f6ba17aed92f8e |
completed | April 16, 2026, 1:35 a.m. |
| PD | Predicate disambiguation | batch_69deca935e2c8190b640987ddfc542b9 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:16 a.m.