Triple
T37018168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quiksilver Pro Gold Coast |
E916138
|
entity |
| Predicate | waveBottomType |
P186918
|
FINISHED |
| Object | sand |
—
|
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: sand | Statement: [Quiksilver Pro Gold Coast, waveBottomType, sand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waveBottomType Context triple: [Quiksilver Pro Gold Coast, waveBottomType, sand]
-
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.
waveSelection
Indicates a relationship where a specific wave or waveform is chosen or designated from among multiple possible options.
-
C.
bottomType
Indicates that the subject entity is classified as a bottom-level or most specific type within a type hierarchy.
-
D.
waveCondition
Indicates that a specified action, state, or relationship holds only under certain wave-related conditions or patterns.
-
E.
waveOrientation
Indicates the direction or alignment of a wave relative to a reference frame or surface.
- 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_69f76e920dc48190acb6bb7ebc4dffab |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fb154c0fe08190a2e41e7a29b6055f |
completed | May 6, 2026, 10:17 a.m. |
| PD | Predicate disambiguation | batch_69f9fecc005c8190be082a8689193745 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fb154b5f8c819089103b41f51a1639 |
completed | May 6, 2026, 10:17 a.m. |
Created at: May 3, 2026, 4:14 p.m.