Triple
T11180958
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2000–01 NBA season |
E264535
|
entity |
| Predicate | MVPPointsPerGame |
P92797
|
FINISHED |
| Object | 31.1 |
—
|
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: 31.1 | Statement: [2000–01 NBA season, MVPPointsPerGame, 31.1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPPointsPerGame Context triple: [2000–01 NBA season, MVPPointsPerGame, 31.1]
-
A.
MVPPoints
Indicates the number of points an entity has earned toward a Most Valuable Player (MVP) recognition or award.
-
B.
MVPStatistic
chosen
Indicates a relationship where a statistical record quantifies or summarizes performance metrics associated with a Most Valuable Player (MVP) designation or award.
-
C.
MVPMinutesPlayed
Indicates the number of minutes played by the player who received the Most Valuable Player (MVP) recognition in a given game or season.
-
D.
MVPGoals
Indicates that an entity has been recognized as the Most Valuable Player (MVP) based on achieving specific performance goals or criteria.
-
E.
MVPRebounds
Indicates that the subject, as a league MVP, recorded a specified number of rebounds (or achieved a notable rebounding performance).
- 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_69d6aa9dafac8190bd90d2c74f661aa7 |
completed | April 8, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69d7e8a7f35481909f35feb94ef10e80 |
completed | April 9, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69d75cf0e6e88190973694abe2990973 |
completed | April 9, 2026, 8:01 a.m. |
Created at: April 8, 2026, 9:29 p.m.