Triple
T2915669
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Seven Mile Beach |
E78599
|
entity |
| Predicate | hasWaveConditions |
P20654
|
FINISHED |
| Object | suitable for surfing |
—
|
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: suitable for surfing | Statement: [Seven Mile Beach, hasWaveConditions, suitable for surfing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaveConditions Context triple: [Seven Mile Beach, hasWaveConditions, suitable for surfing]
-
A.
hasSeaCondition
Indicates that an entity is associated with or characterized by a particular state or condition of the sea.
-
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.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
D.
waveHeightsCanReach
Indicates that the heights of waves are capable of attaining or reaching a specified magnitude or level.
-
E.
hasWindPattern
Indicates that one entity exhibits, is characterized by, or is associated with a particular pattern of wind behavior.
- 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_69ad8b0c2ad081909ff87050ae542bb9 |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad97fd89d88190bc7db4b39058ae3a |
completed | March 8, 2026, 3:38 p.m. |
| PD | Predicate disambiguation | batch_69ad9603ddd88190b8bf91bc7517cc21 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:52 p.m.