Triple
T11033616
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Margate Main Sands |
E260819
|
entity |
| Predicate | hasTide |
P4652
|
FINISHED |
| Object | significant tidal range |
—
|
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: significant tidal range | Statement: [Margate Main Sands, hasTide, significant tidal range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTide Context triple: [Margate Main Sands, hasTide, significant tidal range]
-
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.
containsTidalFeatures
Indicates that one entity exhibits observable tidal features caused by gravitational interactions with another entity.
-
D.
isOnTidalIsland
Indicates that something is located on a tidal island, i.e., land connected to the mainland at low tide and isolated by water at high tide.
-
E.
hasTidalConnection
Indicates that one entity is linked to another through the movement, influence, or exchange of tidal waters.
- 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_69d6aa979bdc8190bf0e79104cc098c1 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d797e709648190adbb05197e15ff76 |
completed | April 9, 2026, 12:13 p.m. |
| PD | Predicate disambiguation | batch_69d7440087ac8190aef2e6f6b13b2635 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:25 p.m.