Triple
T36783059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1997 NBA Finals |
E908824
|
entity |
| Predicate | seriesWinningShotPlayer |
P171306
|
FINISHED |
| Object | Steve Kerr |
—
|
NE NERFINISHED |
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: Steve Kerr | Statement: [1997 NBA Finals, seriesWinningShotPlayer, Steve Kerr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: seriesWinningShotPlayer Context triple: [1997 NBA Finals, seriesWinningShotPlayer, Steve Kerr]
-
A.
championshipWinningShotPlayer
chosen
Indicates the player who made the decisive shot that secured a championship victory for their team.
-
B.
seriesWinningGoalScorer
Indicates the player who scored the decisive goal that clinched victory in a multi-game series.
-
C.
mostValuablePlayerShootoutGoal
Indicates that the referenced player scored the decisive or most significant goal in a shootout, earning recognition as the most valuable player of that shootout.
-
D.
titleWinningGoalScorer
Indicates the player who scored the decisive goal that secured a title or championship in a competition.
-
E.
MVPShotsOnGoal
Indicates that the entity identified as the MVP recorded a certain number of shots on goal in a game or competition.
- 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_69f76e7a937c81909ed7359641e670f6 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd68abf52881909c5a390c362b7c59 |
completed | May 8, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_69fd6812d0c88190930d8fa2d4b92490 |
completed | May 8, 2026, 4:35 a.m. |
Created at: May 3, 2026, 4:12 p.m.