Triple
T25307729
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fantasy 5 |
E634525
|
entity |
| Predicate | hasJackpotType |
P158370
|
FINISHED |
| Object | rolling jackpot |
—
|
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: rolling jackpot | Statement: [Fantasy 5, hasJackpotType, rolling jackpot]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasJackpotType Context triple: [Fantasy 5, hasJackpotType, rolling jackpot]
-
A.
jackpotRule
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.
hasWinnerType
Indicates that an entity has a specific type or category of winner associated with it.
-
D.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
-
E.
minimumJackpot
Indicates that there is a specified lowest possible jackpot amount required or guaranteed in a given context.
- 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_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_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:25 p.m.