Triple
T35374906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | All-Star Game Most Valuable Player Award |
E1021878
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | sports most valuable player award |
C48780
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: sports most valuable player award Context triple: [All-Star Game Most Valuable Player Award, instanceOf, sports most valuable player award]
-
A.
sports industry awards
Sports industry awards are formal recognitions given to organizations, events, brands, and professionals within the sports business ecosystem for excellence in areas such as marketing, media, innovation, and commercial performance.
-
B.
sports architecture award
A sports architecture award is a recognition given to outstanding design and innovation in buildings and facilities created for sporting events and athletic activities.
-
C.
club player of the year award
A club player of the year award is an annual honor given by a sports club to recognize the individual player judged to have delivered the most outstanding performance and contribution over the season.
-
D.
Most Valuable Player-type honor
chosen
A Most Valuable Player-type honor is an award given to the individual judged to have the greatest overall impact, performance, or contribution within a specific competition, season, or event.
-
E.
sports rookie of the year award
A sports rookie of the year award is an annual honor given to the most outstanding first-year player in a league or competition, recognizing exceptional performance and impact during their debut season.
- F. None of above.
Provenance (1 batch)
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_69f76df000488190ab7c97f565677055 |
completed | May 3, 2026, 3:46 p.m. |
Created at: May 3, 2026, 4:03 p.m.