Triple
T37686077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sage Kotsenburg |
E938368
|
entity |
| Predicate | wonInDiscipline |
P84022
|
FINISHED |
| Object | men's slopestyle snowboarding |
—
|
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: men's slopestyle snowboarding | Statement: [Sage Kotsenburg, wonInDiscipline, men's slopestyle snowboarding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wonInDiscipline Context triple: [Sage Kotsenburg, wonInDiscipline, men's slopestyle snowboarding]
-
A.
winnerDiscipline
Indicates that an entity is the winning discipline or field in a given competition, award, or comparative context.
-
B.
wonAt
chosen
Indicates that one entity achieved victory or success in a specific event, competition, or context.
-
C.
hasAwardedDiscipline
Indicates that one entity has formally imposed or granted a disciplinary action or sanction upon another entity.
-
D.
competitionWonWith
Indicates that a competition was won using, involving, or in association with a particular participant, method, tool, or resource.
-
E.
wonTitleFrom
Indicates that one entity obtained a title or championship by defeating or surpassing another specific entity who previously held it.
- 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_69f76ed881408190bc62a969530a4a53 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbb084760c8190a1554985d3c3cb7a |
completed | May 6, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69fbadf3cb548190ba3b7514f76b790a |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.