Triple
T17248704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kiama Surf Beach |
E418692
|
entity |
| Predicate | typicalWaveQuality |
P7231
|
FINISHED |
| Object | moderate to good |
—
|
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 good | Statement: [Kiama Surf Beach, typicalWaveQuality, moderate to good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalWaveQuality Context triple: [Kiama Surf Beach, typicalWaveQuality, moderate to good]
-
A.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
B.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
-
C.
numberOfWaves
Indicates the count of distinct wave events or oscillations associated with a given entity or interaction.
-
D.
hasWaveConsistency
Indicates that the related entities maintain a stable, coherent pattern or behavior across successive waves, phases, or iterations.
-
E.
fieldQuality
chosen
Indicates the assessed level or degree of quality associated with a particular field or attribute in a given context.
- 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_69d886d9ab108190b70edd8d17aa1204 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e42e2569c081908ffd3ee9c76bcc17 |
completed | April 19, 2026, 1:21 a.m. |
| PD | Predicate disambiguation | batch_69e3832553ac819091aa917c84f755b6 |
completed | April 18, 2026, 1:12 p.m. |
Created at: April 10, 2026, 5:39 a.m.