Triple
T22067443
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BetRivers |
E545311
|
entity |
| Predicate | betTypesInclude |
P10208
|
FINISHED |
| Object | moneyline bets |
—
|
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: moneyline bets | Statement: [BetRivers, betTypesInclude, moneyline bets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: betTypesInclude Context triple: [BetRivers, betTypesInclude, moneyline bets]
-
A.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
-
B.
stakesType
Indicates the type or category of stakes involved in a given relationship, action, or situation.
-
C.
includesGameType
chosen
Indicates that one entity contains or supports a particular type or category of game.
-
D.
bettingOdds
Indicates the likelihood or probability of a particular outcome in a bet, typically expressed as numerical odds set for wagering.
-
E.
betting
Indicates engaging in a wager where one party risks something of value on the outcome of an uncertain event involving another entity.
- 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_69e11e344dfc81909b1d88a7221329c7 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12884937c819095d3af69123fa2cb |
completed | April 28, 2026, 9:37 p.m. |
| PD | Predicate disambiguation | batch_69e6f64a6a70819089d1a6c3a2384861 |
completed | April 21, 2026, 4 a.m. |
Created at: April 16, 2026, 8:27 p.m.