Triple
T25307913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powerball |
E634530
|
entity |
| Predicate | jackpotWinCondition |
P151542
|
FINISHED |
| Object | match 5 main numbers plus Powerball |
—
|
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: match 5 main numbers plus Powerball | Statement: [Powerball, jackpotWinCondition, match 5 main numbers plus Powerball]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jackpotWinCondition Context triple: [Powerball, jackpotWinCondition, match 5 main numbers plus Powerball]
-
A.
jackpotRule
chosen
Indicates that a condition or set of conditions qualifies an event, outcome, or entity for a jackpot or special high-value reward.
-
B.
jackpotCap
Indicates a limit or maximum allowable amount set on a jackpot.
-
C.
oddsOfJackpot
Indicates the probability that a given event or scenario will result in hitting the jackpot.
-
D.
hasJackpotType
Indicates that an entity is associated with or classified under a specific type or category of jackpot.
-
E.
minimumJackpot
Indicates that there is a specified lowest possible jackpot amount required or guaranteed in a given context.
- 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_69e75a972c6481909bc11710e8d30a6c |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f4939c49a48190b9fdc2555273915e |
completed | May 1, 2026, 11:50 a.m. |
| PD | Predicate disambiguation | batch_69f4683472ec8190a483b3b8afe71720 |
completed | May 1, 2026, 8:45 a.m. |
Created at: April 21, 2026, 1:25 p.m.