Triple
T25398797
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mega Millions |
E636364
|
entity |
| Predicate | MegaplierFunction |
P104834
|
FINISHED |
| Object | multiplies non-jackpot prizes |
—
|
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: multiplies non-jackpot prizes | Statement: [Mega Millions, MegaplierFunction, multiplies non-jackpot prizes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: MegaplierFunction Context triple: [Mega Millions, MegaplierFunction, multiplies non-jackpot prizes]
-
A.
MegaplierCost
Indicates the monetary amount required to apply the Megaplier option to a lottery ticket or wager.
-
B.
MagicWins
Indicates that one entity achieves victory over another through the use of magic or supernatural powers.
-
C.
oddsOfJackpot
Indicates the probability that a given event or scenario will result in hitting the jackpot.
-
D.
hasAdditionalPrizes
chosen
Indicates that an entity offers or is associated with extra prizes beyond the primary or standard ones.
-
E.
GoldenBallWinner
Indicates that the subject has been awarded the Golden Ball, recognizing them as the best-performing player in a particular football (soccer) tournament 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f8802c819085d55049bd94b075 |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f4683b34748190818428489a226124 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:50 p.m.