Triple
T11180569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Brooks Robinson |
E264526
|
entity |
| Predicate | ALMostValuablePlayer |
P38560
|
FINISHED |
| Object | 1964 |
—
|
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: 1964 | Statement: [Brooks Robinson, ALMostValuablePlayer, 1964]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ALMostValuablePlayer Context triple: [Brooks Robinson, ALMostValuablePlayer, 1964]
-
A.
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.
-
B.
MLBAllStarGameMVP
Indicates that the subject was selected as the Most Valuable Player in a particular Major League Baseball All-Star Game.
-
C.
NFLMVPawards
Indicates the number of times an entity has received the NFL Most Valuable Player (MVP) award.
-
D.
AmericanLeagueMVP
chosen
Indicates that the subject has been awarded the Most Valuable Player (MVP) honor in Major League Baseball’s American League for a given season.
-
E.
MVPHomeRunRunsBattedIn
Indicates that the MVP player hit a home run on the play and was credited with one or more runs batted in (RBIs).
- 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.