Triple
T528445
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NBA 2K League |
E10974
|
entity |
| Predicate | prizePool |
P15222
|
FINISHED |
| Object | multi-million dollar prize pool |
—
|
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: multi-million dollar prize pool | Statement: [NBA 2K League, prizePool, multi-million dollar prize pool]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prizePool Context triple: [NBA 2K League, prizePool, multi-million dollar prize pool]
-
A.
prizeContext
Indicates the situational or contextual circumstances under which a prize is awarded, considered, or relevant.
-
B.
prizeType
Indicates the specific category or kind of prize associated with an entity or event.
-
C.
winnerReceives
Indicates that the entity identified as the winner is granted or awarded the specified item, benefit, or outcome as a result of winning.
-
D.
initialBlockReward
Indicates the reward amount granted for mining or validating the very first block in a blockchain or similar system.
-
E.
thirdPlacePrize
Indicates that an entity receives or is associated with the prize awarded for finishing in third place in a competition or ranking.
- 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_69a2e84b16c4819088d284c47c3a7968 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f1d39b4c81909f265b3501b5ec1d |
completed | Feb. 28, 2026, 1:46 p.m. |
| PD | Predicate disambiguation | batch_69a2f01ac3ec8190a94a05955532c7fa |
completed | Feb. 28, 2026, 1:39 p.m. |
| PDg | Predicate description generation | batch_69a2f0dcff1881909c18e8c599c150a1 |
completed | Feb. 28, 2026, 1:42 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.