Triple
T27357477
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1993 NBA Finals |
E685723
|
entity |
| Predicate | JordanFinalsMVPNumber |
P162225
|
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: [1993 NBA Finals, JordanFinalsMVPNumber, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: JordanFinalsMVPNumber Context triple: [1993 NBA Finals, JordanFinalsMVPNumber, 3]
-
A.
finalsMVPInGameName
Indicates that a player was named the Most Valuable Player (MVP) in a specific finals game identified by its name.
-
B.
finalsMVPFor
Indicates that one entity is the Most Valuable Player (MVP) specifically for the finals of a competition, series, or tournament associated with another entity.
-
C.
finalsMVPAssistsPerGame
Indicates the average number of assists per game a player records during the NBA Finals in a season where they are named Finals MVP.
-
D.
finalsMVPWinnerFromTeam
Indicates that the specified player won the Finals MVP award while playing for the specified team.
-
E.
NBAFinalsMVP
Indicates that the person was awarded the Most Valuable Player (MVP) honor for their performance in an NBA Finals series.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f62c20321481908ba574ad96d93013 |
completed | May 2, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69f620e4b1c88190a17940251abc68fd |
completed | May 2, 2026, 4:05 p.m. |
| PDg | Predicate description generation | batch_69f621fbfc2c8190bfa802d7dc0f6aa4 |
completed | May 2, 2026, 4:10 p.m. |
Created at: April 27, 2026, 11:52 a.m.