Triple
T19168559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tuncurry Beach |
E469250
|
entity |
| Predicate | waveClimate |
P20654
|
FINISHED |
| Object | moderate to high energy surf |
—
|
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: moderate to high energy surf | Statement: [Tuncurry Beach, waveClimate, moderate to high energy surf]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waveClimate Context triple: [Tuncurry Beach, waveClimate, moderate to high energy surf]
-
A.
waveCondition
Indicates that a specified action, state, or relationship holds only under certain wave-related conditions or patterns.
-
B.
hasWaveClimate
chosen
Indicates a relationship where a location or coastal area is characterized by a particular pattern or regime of wave conditions (such as height, period, and direction).
-
C.
waveDirection
Indicates the direction in which a wave is propagating or traveling relative to a reference frame.
-
D.
waveHeightsCanReach
Indicates that the heights of waves are capable of attaining or reaching a specified magnitude or level.
-
E.
oceanInfluence
Indicates how the presence, properties, or behavior of an ocean affects another entity, condition, or process.
- 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_69d8dd09d5a081909ae43c286651ae5a |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5f16132e081908c6b8d576163316e |
completed | April 20, 2026, 9:26 a.m. |
| PD | Predicate disambiguation | batch_69e4b9b83d6881908e6271c620f74100 |
completed | April 19, 2026, 11:17 a.m. |
Created at: April 10, 2026, 12:06 p.m.