Triple
T4828147
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rockpiles surf break |
E107875
|
entity |
| Predicate | hasWaveCharacteristic |
P56830
|
FINISHED |
| Object | powerful |
—
|
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: powerful | Statement: [Rockpiles surf break, hasWaveCharacteristic, powerful]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWaveCharacteristic Context triple: [Rockpiles surf break, hasWaveCharacteristic, powerful]
-
A.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
-
B.
waveCharacteristic
chosen
Indicates that one entity specifies or describes a particular property or feature of a wave associated with another entity.
-
C.
hasWaveConsistency
Indicates that the related entities maintain a stable, coherent pattern or behavior across successive waves, phases, or iterations.
-
D.
numberOfWaves
Indicates the count of distinct wave events or oscillations associated with a given entity or interaction.
-
E.
hasCharacteristic
Indicates that an entity possesses, exhibits, or is defined by a particular attribute, feature, or quality.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ddd17d881909f7731ff2b460e83 |
completed | March 20, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69bd6c1fe130819087ae01309f96a0c8 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.