Triple
T36231344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1978 Major League Baseball season |
E891252
|
entity |
| Predicate | WorldSeriesMVPTeam |
P2175
|
FINISHED |
| Object | New York Yankees |
—
|
NE NERFINISHED |
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: New York Yankees | Statement: [1978 Major League Baseball season, WorldSeriesMVPTeam, New York Yankees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: WorldSeriesMVPTeam Context triple: [1978 Major League Baseball season, WorldSeriesMVPTeam, New York Yankees]
-
A.
WorldSeriesChampion
chosen
Indicates that a team or individual has won the championship title in a given season of the World Series.
-
B.
coWorldSeriesMVPWith
Indicates that two players shared the World Series Most Valuable Player (MVP) award in the same year.
-
C.
worldSeriesMVP
Indicates that the subject was selected as the Most Valuable Player (MVP) of a particular World Series.
-
D.
MVPHomeRunPitcherTeam
Indicates that the team is the one for which the pitcher played when throwing the home run pitch associated with the MVP event.
-
E.
finalsMVPWinnerFromTeam
Indicates that the specified player won the Finals MVP award while playing for the specified team.
- 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_69f76e4387048190a1b27bcbf4ec7423 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69feabcda59481908f2bc13b46fcced1 |
completed | May 9, 2026, 3:36 a.m. |
| PD | Predicate disambiguation | batch_69feaabd63f88190b30dcf6dd2ea39d1 |
completed | May 9, 2026, 3:32 a.m. |
Created at: May 3, 2026, 4:09 p.m.