Triple
T8514808
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 NHL All-Star Game |
E201545
|
entity |
| Predicate | MVPShotsOnGoal |
P82928
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [1999 NHL All-Star Game, MVPShotsOnGoal, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPShotsOnGoal Context triple: [1999 NHL All-Star Game, MVPShotsOnGoal, 3]
-
A.
MVPGoals
Indicates that an entity has been recognized as the Most Valuable Player (MVP) based on achieving specific performance goals or criteria.
-
B.
MVPThreePointersMade
Indicates the number of three-point field goals successfully made by the MVP in a game or season.
-
C.
MVPPeriodGoals
Indicates the number of goals a player scored during the period in which they were recognized as the Most Valuable Player (MVP).
-
D.
MVPThreePointersAttempted
Indicates the number of three-point shots attempted by the MVP in a given context or period.
-
E.
MVPPoints
Indicates the number of points an entity has earned toward a Most Valuable Player (MVP) recognition or award.
- F. None of above. chosen
Provenance (4 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_69ca8320e5748190ac2c585a0bba8193 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe60e12848190a4a3dfa457aef275 |
completed | March 31, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69cbd10cfd208190a519049fad32c508 |
completed | March 31, 2026, 1:50 p.m. |
| PDg | Predicate description generation | batch_69cbe12dd0b88190a38ec4d15dcc870b |
completed | March 31, 2026, 2:58 p.m. |
Created at: March 30, 2026, 6:15 p.m.