Triple
T15605876
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1984 NBA Finals |
E375158
|
entity |
| Predicate | MVPNumber |
P86497
|
FINISHED |
| Object | 33 |
—
|
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: 33 | Statement: [1984 NBA Finals, MVPNumber, 33]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPNumber Context triple: [1984 NBA Finals, MVPNumber, 33]
-
A.
MVPJerseyNumber
chosen
Indicates the jersey number worn by the player who received the MVP (Most Valuable Player) award in a given context.
-
B.
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).
-
C.
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.
-
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.
MVPInLeague
Indicates that an entity was selected as the Most Valuable Player (MVP) within a particular league for a given season or time period.
- 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_69d85ccf2794819096cda4cbcb02d478 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69e04e7d9328819090e93d55881269a5 |
completed | April 16, 2026, 2:50 a.m. |
| PD | Predicate disambiguation | batch_69deda844af081909e658ebc9d9b403d |
completed | April 15, 2026, 12:23 a.m. |
Created at: April 10, 2026, 4:12 a.m.