Triple
T24734632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1994 Major League Baseball season |
E618376
|
entity |
| Predicate | mvpAwardNL |
P43192
|
FINISHED |
| Object | not awarded |
—
|
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: not awarded | Statement: [1994 Major League Baseball season, mvpAwardNL, not awarded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mvpAwardNL Context triple: [1994 Major League Baseball season, mvpAwardNL, not awarded]
-
A.
mvpDistinction
Indicates that an entity has been recognized with a Most Valuable Player (MVP) distinction or award in a given context or event.
-
B.
MVPTypeAward
Indicates that an entity has received a specific type or category of Most Valuable Player (MVP) award.
-
C.
mvpAwardAL
Indicates that a player has received the Most Valuable Player (MVP) award in the American League.
-
D.
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.
-
E.
MVPInLeague
chosen
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_69e2fab772608190b74163751047ff50 |
completed | April 18, 2026, 3:29 a.m. |
| NER | Named-entity recognition | batch_69f422aee0408190899efe7e24ef2b40 |
completed | May 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69f420e92cc88190a803aecdae78a051 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:03 a.m.