Triple
T7684783
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2013 Major League Baseball All-Star Game |
E174087
|
entity |
| Predicate | MVPRunsAllowed |
P78916
|
FINISHED |
| Object | 0 |
—
|
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: 0 | Statement: [2013 Major League Baseball All-Star Game, MVPRunsAllowed, 0]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPRunsAllowed Context triple: [2013 Major League Baseball All-Star Game, MVPRunsAllowed, 0]
-
A.
MVPType
Indicates the specific category or role of a person or entity designated as the “Most Valuable Player” (MVP) within a given context or system.
-
B.
MVPThrows
Indicates that a most valuable player (MVP) performs a throwing action toward or involving another entity.
-
C.
MVPReceives
Indicates that an entity designated as the MVP is the recipient of something (such as an award, recognition, or benefit) from another entity or event.
-
D.
numberOfTimesMVP
Indicates the number of times an entity has been recognized as the Most Valuable Player (MVP).
-
E.
MVP
Indicates that an entity has been selected or recognized as the “Most Valuable Player,” i.e., the most outstanding or impactful participant within a specific game, season, event, or context.
- 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_69c6995840408190a19de6c51090f46f |
completed | March 27, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69c7048b0b448190889bd40e0a38e51a |
completed | March 27, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69c701618d3481908be84b76f36ac5a1 |
completed | March 27, 2026, 10:14 p.m. |
| PDg | Predicate description generation | batch_69c7048a01508190bc2e9ae8b863486c |
completed | March 27, 2026, 10:28 p.m. |
Created at: March 27, 2026, 4:02 p.m.