Triple
T25307928
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Powerball |
E634530
|
entity |
| Predicate | jackpotRolloverPolicy |
P151542
|
FINISHED |
| Object | jackpot increases when not won |
—
|
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: jackpot increases when not won | Statement: [Powerball, jackpotRolloverPolicy, jackpot increases when not won]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jackpotRolloverPolicy Context triple: [Powerball, jackpotRolloverPolicy, jackpot increases when not won]
-
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.
jackpotPayoutOptions
Indicates the available ways in which a jackpot can be paid out to a winner (e.g., lump sum, annuity, or other payout structures).
-
D.
oddsOfJackpot
Indicates the probability that a given event or scenario will result in hitting the jackpot.
-
E.
hasJackpot
Indicates that an entity possesses or offers a jackpot prize or top reward.
- 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_69f55e519978819087a1676564a74630 |
completed | May 2, 2026, 2:15 a.m. |
| PD | Predicate disambiguation | batch_69f4a0edd10c81908a052ab864d57c54 |
completed | May 1, 2026, 12:47 p.m. |
Created at: April 21, 2026, 1:25 p.m.