Triple
T17724019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rip Curl surf team |
E442413
|
entity |
| Predicate | sponsoredAthletes |
P737
|
FINISHED |
| Object | elite surfers |
—
|
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: elite surfers | Statement: [Rip Curl surf team, sponsoredAthletes, elite surfers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sponsoredAthletes Context triple: [Rip Curl surf team, sponsoredAthletes, elite surfers]
-
A.
sportsSponsored
chosen
Indicates that one entity provides financial or material sponsorship to support another entity’s sports-related activities or events.
-
B.
sponsorSport
Indicates that one entity financially or materially supports a sport or sporting activity, typically in exchange for promotion or association.
-
C.
alsoSponsorsSport
Indicates that an entity that sponsors one sport also sponsors another sport.
-
D.
athletesFrom
Indicates that one or more athletes originate from, represent, or are associated with a particular place or organization.
-
E.
representedAthlete
Indicates that one entity serves as an official representative or agent for a particular athlete.
- 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_69d8b9ec79688190b86bdcef85a7b3aa |
completed | April 10, 2026, 8:50 a.m. |
| NER | Named-entity recognition | batch_69e4748900608190bf5ba04415edaffc |
completed | April 19, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69e3cde815e08190881972e2d80d151e |
completed | April 18, 2026, 6:31 p.m. |
Created at: April 10, 2026, 10:07 a.m.