Triple
T18618088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mavericks surf break |
E455080
|
entity |
| Predicate | popularizedInSurfing |
P2352
|
FINISHED |
| Object | 1990s |
—
|
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: 1990s | Statement: [Mavericks surf break, popularizedInSurfing, 1990s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: popularizedInSurfing Context triple: [Mavericks surf break, popularizedInSurfing, 1990s]
-
A.
popularizedIn
chosen
Indicates that something became widely known, accepted, or fashionable within a particular place, time period, or context.
-
B.
learnsToSurfFrom
Indicates that one entity acquires or practices surfing skills under the instruction, guidance, or example of another entity.
-
C.
hasSurfCulture
Indicates that there is a notable presence or tradition of surfing-related practices, values, and lifestyle associated with the subject.
-
D.
popularizedBy
Indicates that something became widely known, accepted, or fashionable as a result of the influence or actions of a particular agent.
-
E.
hasSurfBreak
Indicates a relationship where a location or area contains or is associated with a specific surf break suitable for surfing.
- 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.