Triple
T26417054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Roulette |
E664124
|
entity |
| Predicate | hasInsideBet |
P167287
|
FINISHED |
| Object | straight-up bet |
—
|
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: straight-up bet | Statement: [Roulette, hasInsideBet, straight-up bet]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasInsideBet Context triple: [Roulette, hasInsideBet, straight-up bet]
-
A.
hasOutsideBet
Indicates that an entity has placed or holds a bet on an outcome considered an outside or less likely option in a given betting context.
-
B.
hasBetType
chosen
Indicates that an entity is associated with or classified under a specific type or category of bet.
-
C.
hasBettingStructure
Indicates that there is a specific set of rules or format governing how bets are placed and progressed in a game or wagering context.
-
D.
hasForcedBet
Indicates that one party is required to place a bet or wager under compulsory or non-voluntary conditions.
-
E.
hasToteBetting
Indicates that an entity offers or is associated with pari-mutuel (tote) betting services or facilities.
- 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_69ee883a04ec81908883c4559f8c7e24 |
completed | April 26, 2026, 9:48 p.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 26, 2026, 11:41 p.m.