Triple
T3967261
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Saratoga Race Course |
E92245
|
entity |
| Predicate | hasBetting |
P47794
|
FINISHED |
| Object | pari-mutuel wagering |
—
|
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: pari-mutuel wagering | Statement: [Saratoga Race Course, hasBetting, pari-mutuel wagering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBetting Context triple: [Saratoga Race Course, hasBetting, pari-mutuel wagering]
-
A.
hasToteBetting
chosen
Indicates that an entity offers or is associated with pari-mutuel (tote) betting services or facilities.
-
B.
betting
Indicates engaging in a wager where one party risks something of value on the outcome of an uncertain event involving another entity.
-
C.
hasCasino
Indicates that an entity includes, contains, or is associated with a casino facility or gambling establishment.
-
D.
usedInBettingLines
Indicates that something (such as data, statistics, or an event) is employed as a factor or component in determining betting lines or odds.
-
E.
hasBookmakers
Indicates that an entity is associated with or utilizes one or more bookmakers for betting or odds-setting activities.
- 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_69aed96624188190ac8c45bb57ab72b5 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaca33e4819091957c7915857a42 |
completed | March 9, 2026, 4:52 p.m. |
| PD | Predicate disambiguation | batch_69aef8f252b081909749d40440d372b2 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:32 p.m.