Triple
T17288390
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hot Water Beach |
E419716
|
entity |
| Predicate | tideWindow |
P126821
|
FINISHED |
| Object | approximately two hours either side of low tide |
—
|
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: approximately two hours either side of low tide | Statement: [Hot Water Beach, tideWindow, approximately two hours either side of low tide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: tideWindow Context triple: [Hot Water Beach, tideWindow, approximately two hours either side of low tide]
-
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.
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.
-
C.
atEbbTide
Indicates that the related event or state occurs when the tide is at its lowest level (ebb tide).
-
D.
isTidal
Indicates that something is influenced or driven by tidal forces or tidal movements.
-
E.
hasTidalRange
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. chosen
Provenance (4 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_69d886db32608190a61e18862c5a8af6 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43781b7808190a0528ee9c54a0c66 |
completed | April 19, 2026, 2:01 a.m. |
| PD | Predicate disambiguation | batch_69e3b0118ad08190b119cd219c68ba67 |
completed | April 18, 2026, 4:23 p.m. |
| PDg | Predicate description generation | batch_69e3b2a225b08190a50f984caa6513b9 |
completed | April 18, 2026, 4:34 p.m. |
Created at: April 10, 2026, 5:40 a.m.