Triple
T27353409
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Happy Valley Racecourse |
E685620
|
entity |
| Predicate | hasBettingSystem |
P47794
|
FINISHED |
| Object | pari-mutuel betting |
—
|
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 betting | Statement: [Happy Valley Racecourse, hasBettingSystem, pari-mutuel betting]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBettingSystem Context triple: [Happy Valley Racecourse, hasBettingSystem, pari-mutuel betting]
-
A.
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.
-
B.
hasBetType
Indicates that an entity is associated with or classified under a specific type or category of bet.
-
C.
usesBettingStructure
Indicates that one entity employs or follows a particular betting structure in the context of wagering or games.
-
D.
hasToteBetting
chosen
Indicates that an entity offers or is associated with pari-mutuel (tote) betting services or facilities.
-
E.
bettingStructure
Indicates the rules and format governing how bets are placed, sized, and progressed within a wagering or game context.
- 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_69ef14887c288190931b8431fdbf53c4 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 27, 2026, 11:50 a.m.