Triple
T28192462
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2021 NBA Finals |
E716352
|
entity |
| Predicate | MVPPointsInClinchingGame |
P8918
|
FINISHED |
| Object | 50 |
—
|
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: 50 | Statement: [2021 NBA Finals, MVPPointsInClinchingGame, 50]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPPointsInClinchingGame Context triple: [2021 NBA Finals, MVPPointsInClinchingGame, 50]
-
A.
MVPPoints
chosen
Indicates the number of points an entity has earned toward a Most Valuable Player (MVP) recognition or award.
-
B.
MVPGoals
Indicates that an entity has been recognized as the Most Valuable Player (MVP) based on achieving specific performance goals or criteria.
-
C.
MVPPerformance
Indicates that an entity delivered a standout, most valuable player–level performance in a given context or event.
-
D.
MVPStatistic
Indicates a relationship where a statistical record quantifies or summarizes performance metrics associated with a Most Valuable Player (MVP) designation or award.
-
E.
MVPrecord
Indicates that an entity holds the record for having won the Most Valuable Player (MVP) award the greatest number of times (or in a notable record-setting manner).
- 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_69efd6b612f48190a72012b520afbd10 |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f642ce9aec8190bb3e76ca66824af7 |
completed | May 2, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69f63c6c1a948190b68c0f92c264cc0c |
completed | May 2, 2026, 6:03 p.m. |
Created at: April 27, 2026, 10:26 p.m.