Triple
T18618160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mavericks |
E455082
|
entity |
| Predicate | hasTypicalBigWaveRange |
P41302
|
FINISHED |
| Object | 25 to 60 feet on the face |
—
|
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: 25 to 60 feet on the face | Statement: [Mavericks, hasTypicalBigWaveRange, 25 to 60 feet on the face]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTypicalBigWaveRange Context triple: [Mavericks, hasTypicalBigWaveRange, 25 to 60 feet on the face]
-
A.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
-
B.
waveHeightsCanReach
chosen
Indicates that the heights of waves are capable of attaining or reaching a specified magnitude or level.
-
C.
hasBreakwater
Indicates that a structure or location is equipped with or associated with a breakwater that provides protection from waves or erosion.
-
D.
hasMaximumTidalBoreHeight
Indicates that one entity has a specified greatest recorded or expected height of its tidal bore.
-
E.
hasWave
Indicates that one entity possesses, exhibits, or is associated with a particular wave or waveform.
- 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_69d8d38bbe7c8190bdec3138e7d413c9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e54d06c1f8819094fbfa56eca07eaa |
completed | April 19, 2026, 9:45 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
Created at: April 10, 2026, 11:46 a.m.