Triple
T4830859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NPB All-Star Game |
E107940
|
entity |
| Predicate | MVPSelection |
P2630
|
FINISHED |
| Object | per game |
—
|
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: per game | Statement: [NPB All-Star Game, MVPSelection, per game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MVPSelection Context triple: [NPB All-Star Game, MVPSelection, per game]
-
A.
MVPawardYear
Indicates the year in which an entity received a Most Valuable Player (MVP) award.
-
B.
MVPInLeague
Indicates that an entity was selected as the Most Valuable Player (MVP) within a particular league for a given season or time period.
-
C.
MVPPoints
Indicates the number of points an entity has earned toward a Most Valuable Player (MVP) recognition or award.
-
D.
MVP
chosen
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.
-
E.
MVPConference
Indicates a relationship where an entity serves as the most valuable player (MVP) specifically for a given conference within a league or competition.
- 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_69bd43fac8188190803f0327190621e4 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6ff981fc819080d4466c6fe06cf3 |
completed | March 20, 2026, 4:04 p.m. |
| PD | Predicate disambiguation | batch_69bd6c21c7f08190846049d31fdfa144 |
completed | March 20, 2026, 3:47 p.m. |
Created at: March 20, 2026, 1:24 p.m.