Triple
T22213194
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aaron Gordon |
E549006
|
entity |
| Predicate | notableDunk |
P9490
|
FINISHED |
| Object | over mascot Stuff the Magic Dragon in 2016 contest |
—
|
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: over mascot Stuff the Magic Dragon in 2016 contest | Statement: [Aaron Gordon, notableDunk, over mascot Stuff the Magic Dragon in 2016 contest]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableDunk Context triple: [Aaron Gordon, notableDunk, over mascot Stuff the Magic Dragon in 2016 contest]
-
A.
maximumScorePerDunk
Indicates the highest number of points that can be awarded for a single dunk action in the given context.
-
B.
notableAttempt
Indicates that an entity made a significant or noteworthy effort to perform or achieve another entity or outcome.
-
C.
notablePlay
chosen
Indicates that a particular play is especially famous, significant, or noteworthy in relation to the entity it is associated with.
-
D.
SlamDunkContestWinner
Indicates that the subject is the winner of a slam dunk contest competition.
-
E.
playedBasketballFor
Indicates that one entity was a member of and competed for another entity’s basketball team.
- 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_69e11e3f7e04819089806d81d5ac431e |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12b2d607c81909511761b5563ddee |
completed | April 28, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69e71b4dcc408190a30429fb08fcf39e |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.