Triple
T26513743
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Surf League Championship Tour event at Teahupoʻo |
E669756
|
entity |
| Predicate | waveFeature |
P56830
|
FINISHED |
| Object | shallow inside reef |
—
|
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: shallow inside reef | Statement: [World Surf League Championship Tour event at Teahupoʻo, waveFeature, shallow inside reef]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: waveFeature Context triple: [World Surf League Championship Tour event at Teahupoʻo, waveFeature, shallow inside reef]
-
A.
waveCharacteristic
chosen
Indicates that one entity specifies or describes a particular property or feature of a wave associated with another entity.
-
B.
waveType
Indicates the specific kind or category of wave associated with an entity or interaction (e.g., type of signal, motion, or oscillation).
-
C.
waveSource
Indicates that an entity serves as the origin or emitter of a wave affecting another entity or region.
-
D.
waveLength
Indicates the distance between successive corresponding points (such as peaks) of a wave associated with the related entities.
-
E.
waveSelection
Indicates a relationship where a specific wave or waveform is chosen or designated from among multiple possible options.
- 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_69eeb31b6dcc8190b30632dc3928a0c0 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a17a7788190946f7e32d63cd43f |
completed | May 2, 2026, 3:36 p.m. |
| PD | Predicate disambiguation | batch_69f611ab768c8190b1849c15a3e59dda |
completed | May 2, 2026, 3 p.m. |
Created at: April 27, 2026, 1:22 a.m.