Triple
T30138476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saunton Sands |
E766062
|
entity |
| Predicate | hasTideRange |
P4652
|
FINISHED |
| Object | large 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: large tidal range | Statement: [Saunton Sands, hasTideRange, large tidal range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTideRange Context triple: [Saunton Sands, hasTideRange, large 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.
isTidalInfluenced
Indicates that an entity is affected or controlled by tidal forces or tidal conditions.
-
C.
hasTidalLimitAt
Indicates that the extent or boundary of tidal influence on a water body or watercourse occurs at the specified location or point.
-
D.
hasTidalConstituent
Indicates that something includes or is associated with a specific tidal constituent as part of its tidal characteristics or behavior.
-
E.
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.
- 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_69f2247909048190ae86c2160cf8b566 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7b0e5744c8190a22c1e1d6fcfa466 |
completed | May 3, 2026, 8:32 p.m. |
| PD | Predicate disambiguation | batch_69f7ab70d034819080295628497d8582 |
completed | May 3, 2026, 8:09 p.m. |
Created at: April 29, 2026, 7:17 p.m.