Triple
T266580
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA All-Star Game 2020 |
E5742
|
entity |
| Predicate | MVPMinutesPlayed |
P8923
|
FINISHED |
| Object | 20 |
—
|
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: 20 | Statement: [NBA All-Star Game 2020, MVPMinutesPlayed, 20]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPMinutesPlayed Context triple: [NBA All-Star Game 2020, MVPMinutesPlayed, 20]
-
A.
MVPGoals
Indicates that an entity has been recognized as the Most Valuable Player (MVP) based on achieving specific performance goals or criteria.
-
B.
MVP
Indicates that an entity has been selected or recognized as the “Most Valuable Player,” i.e., the most outstanding or impactful participant within a specific game, season, event, or context.
-
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.
MVPRecord
Indicates that an entity holds a record for the most valuable player (MVP) distinction within a particular context, competition, or time period.
-
E.
NBAAllStarGameMVPawards
Indicates that the subject has received one or more NBA All-Star Game Most Valuable Player (MVP) awards.
- 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_69a2587daeb081909591b9d30f80a271 |
completed | Feb. 28, 2026, 2:52 a.m. |
| NER | Named-entity recognition | batch_69a25d90bab48190b3ef97a451653b7f |
completed | Feb. 28, 2026, 3:14 a.m. |
| PD | Predicate disambiguation | batch_69a25b6f60b081908fc6467800a8849e |
completed | Feb. 28, 2026, 3:05 a.m. |
| PDg | Predicate description generation | batch_69a25c8ae480819094f6d1bb0a6d2eb2 |
completed | Feb. 28, 2026, 3:10 a.m. |
Created at: Feb. 28, 2026, 2:56 a.m.