Triple
T21969937
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whiteford Sands |
E542558
|
entity |
| Predicate | tide |
P4652
|
FINISHED |
| Object | macrotidal (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: macrotidal (large tidal range) | Statement: [Whiteford Sands, tide, macrotidal (large tidal range)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tide Context triple: [Whiteford Sands, tide, macrotidal (large tidal range)]
-
A.
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.
-
B.
receivesTideFrom
Indicates that one entity obtains or is affected by tidal influence originating from another entity.
-
C.
tidalCycle
Indicates the recurring pattern or phase of tides associated with an entity, such as its current position within a tidal rise-and-fall cycle.
-
D.
atEbbTide
Indicates that the related event or state occurs when the tide is at its lowest level (ebb tide).
-
E.
hasTidalRange
chosen
Indicates the relationship between a location or body of water and the magnitude of difference between its high and low tide levels.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1245e4ebc8190968108cc95a22fe4 |
completed | April 28, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69e6f601f2188190893bcdde0cf58ad6 |
completed | April 21, 2026, 3:58 a.m. |
Created at: April 16, 2026, 8:02 p.m.