Triple
T26889708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2016 Rose Bowl |
E677138
|
entity |
| Predicate | mostValuablePlayerJerseyNumber |
P86497
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [2016 Rose Bowl, mostValuablePlayerJerseyNumber, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mostValuablePlayerJerseyNumber Context triple: [2016 Rose Bowl, mostValuablePlayerJerseyNumber, 5]
-
A.
MVPJerseyNumber
chosen
Indicates the jersey number worn by the player who received the MVP (Most Valuable Player) award in a given context.
-
B.
jerseyNumber
Indicates the specific uniform number assigned to and worn by an individual, typically in a sports context.
-
C.
mostValuablePlayerAward
Indicates that an entity has received a "Most Valuable Player" award recognizing it as the most outstanding performer in a particular context or competition.
-
D.
hasJerseyNumberRetired
Indicates that an entity has had its jersey number officially retired, typically in recognition of its contributions or achievements.
-
E.
leagueRetiredNumberBy
Indicates that a sports league has officially retired a specific jersey number in honor of a particular person or entity.
- 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_69eee9bc0c90819085608c8bdc513a57 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69f61f66aeac819080748c6a0fb95f9b |
completed | May 2, 2026, 3:59 p.m. |
| PD | Predicate disambiguation | batch_69f611af72ac819094598dd2530d7411 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 5:44 a.m.