Triple
T20130977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dunbogan Beach |
E490888
|
entity |
| Predicate | waveEnvironment |
P138788
|
FINISHED |
| Object | surf beach |
—
|
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: surf beach | Statement: [Dunbogan Beach, waveEnvironment, surf beach]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waveEnvironment Context triple: [Dunbogan Beach, waveEnvironment, surf beach]
-
A.
waveCondition
Indicates that a specified action, state, or relationship holds only under certain wave-related conditions or patterns.
-
B.
waveDirection
Indicates the direction in which a wave is propagating or traveling relative to a reference frame.
-
C.
wavePower
Indicates that an entity possesses, generates, or is characterized by power derived from ocean surface waves.
-
D.
waveCharacteristic
Indicates that one entity specifies or describes a particular property or feature of a wave associated with another entity.
-
E.
waveSource
Indicates that an entity serves as the origin or emitter of a wave affecting another entity or region.
- 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_69da62651a0c8190a3e05e95e056a66b |
completed | April 11, 2026, 3:01 p.m. |
| NER | Named-entity recognition | batch_69e6676183dc8190b65d0def681aaa1e |
completed | April 20, 2026, 5:50 p.m. |
| PD | Predicate disambiguation | batch_69e54cfb0d0081908e789b9b57e96668 |
completed | April 19, 2026, 9:45 p.m. |
| PDg | Predicate description generation | batch_69e54fc2bc3c819088c33cd263303433 |
completed | April 19, 2026, 9:57 p.m. |
Created at: April 11, 2026, 11:31 p.m.