Triple
T34040612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tipping Point |
E872931
|
entity |
| Predicate | jackpotAwardedFor |
P165209
|
FINISHED |
| Object | dropping jackpot counter |
—
|
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: dropping jackpot counter | Statement: [Tipping Point, jackpotAwardedFor, dropping jackpot counter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: jackpotAwardedFor Context triple: [Tipping Point, jackpotAwardedFor, dropping jackpot counter]
-
A.
jackpotCap
Indicates a limit or maximum allowable amount set on a jackpot.
-
B.
hasJackpot
Indicates that an entity possesses or offers a jackpot prize or top reward.
-
C.
jackpotFeature
chosen
Indicates a special game event or mechanic that awards a large, often top-tier prize when triggered.
-
D.
jackpotRule
Indicates that a condition or set of conditions qualifies an event, outcome, or entity for a jackpot or special high-value reward.
-
E.
oddsOfJackpot
Indicates the probability that a given event or scenario will result in hitting the jackpot.
- 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_69f349a3363081909cea4c9a848cefe2 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f70b966860819089cf92927f47c5f1 |
completed | May 3, 2026, 8:47 a.m. |
| PD | Predicate disambiguation | batch_69f70ac0170c819098e3b8e41d02efef |
completed | May 3, 2026, 8:43 a.m. |
Created at: May 1, 2026, 1:51 a.m.