Triple
T31651759
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Laureus World Action Sportsperson of the Year |
E807747
|
entity |
| Predicate | eligibleSport |
P67409
|
FINISHED |
| Object | surfing |
—
|
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: surfing | Statement: [Laureus World Action Sportsperson of the Year, eligibleSport, surfing]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eligibleSport Context triple: [Laureus World Action Sportsperson of the Year, eligibleSport, surfing]
-
A.
includesSport
Indicates that one entity contains, offers, or features a particular sport as part of its activities, content, or composition.
-
B.
relatedSport
chosen
Indicates that there is an association or connection between an entity and a particular sport.
-
C.
sportEventType
Indicates the specific kind or category of sport associated with a given sporting event.
-
D.
sportCategory
Indicates that one entity is classified as a type or category of sport to which the other entity (typically a specific sport or sporting event) belongs.
-
E.
sportFounded
Indicates that an entity (such as a sports team, club, or organization) was established or created by another entity.
- 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_69f348daf95c81908b4c985b7ddcd0b3 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6d16f5cb881908eed141afaaa0b51 |
completed | May 3, 2026, 4:39 a.m. |
| PD | Predicate disambiguation | batch_69f6cfe45554819089cbbd538d992132 |
completed | May 3, 2026, 4:32 a.m. |
Created at: April 30, 2026, 10:53 p.m.