Triple

T15196579
Position Surface form Disambiguated ID Type / Status
Subject 1991 MLB All-Star Game E363151 entity
Predicate MVPPerformance P117083 FINISHED
Object 3-run home run 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-run home run | Statement: [1991 MLB All-Star Game, MVPPerformance, 3-run home run]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: MVPPerformance
Context triple: [1991 MLB All-Star Game, MVPPerformance, 3-run home run]
  • A. MVPStatistic
    Indicates a relationship where a statistical record quantifies or summarizes performance metrics associated with a Most Valuable Player (MVP) designation or award.
  • B. MVPPoints
    Indicates the number of points an entity has earned toward a Most Valuable Player (MVP) recognition or award.
  • C. MVPrecord
    Indicates that an entity holds the record for having won the Most Valuable Player (MVP) award the greatest number of times (or in a notable record-setting manner).
  • D. MVPGoals
    Indicates that an entity has been recognized as the Most Valuable Player (MVP) based on achieving specific performance goals or criteria.
  • E. MVPInLeague
    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. 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_69d85a0b78bc8190b6e5ad51a2c4cfc5 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e0067fcc788190abdc083d4eadeb36 completed April 15, 2026, 9:43 p.m.
PD Predicate disambiguation batch_69deb97bd8bc8190b2ad4888f97cf963 completed April 14, 2026, 10:02 p.m.
PDg Predicate description generation batch_69dec72059c08190a34f513a00185b08 completed April 14, 2026, 11 p.m.
Created at: April 10, 2026, 3:10 a.m.