Triple
T37898971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Surf League Championship Tour |
E945354
|
entity |
| Predicate | hasSeasonEnd |
P198438
|
FINISHED |
| Object | crowning of world champions |
—
|
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: crowning of world champions | Statement: [World Surf League Championship Tour, hasSeasonEnd, crowning of world champions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSeasonEnd Context triple: [World Surf League Championship Tour, hasSeasonEnd, crowning of world champions]
-
A.
endSeason
Indicates the action or event of bringing a particular season, series, or period to a close.
-
B.
hasSeasonOutcome
chosen
Indicates the result or final status achieved by an entity over the course of a specific season.
-
C.
regularSeasonEndEvent
Indicates the event that marks the conclusion of a regular season in a competition or league.
-
D.
participationEndSeason
Indicates the season in which a participation, involvement, or membership in an activity or organization comes to an end.
-
E.
season1EndDate
Indicates the calendar date on which the first season of something (e.g., a show, competition, or series) concludes.
- 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_69f76ef0e8708190987c7254ed8c7abe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00ae638fcc819096537b2c21366161 |
completed | May 10, 2026, 4:12 p.m. |
| PD | Predicate disambiguation | batch_6a00ae0551988190bcb3564ed9af2847 |
completed | May 10, 2026, 4:10 p.m. |
Created at: May 3, 2026, 4:19 p.m.