Triple
T30836463
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Los Alamitos Race Course |
E785378
|
entity |
| Predicate | hasSimulcastWagering |
P148249
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Los Alamitos Race Course, hasSimulcastWagering, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSimulcastWagering Context triple: [Los Alamitos Race Course, hasSimulcastWagering, yes]
-
A.
wageringAvailable
chosen
Indicates that it is possible to place bets or wagers on the associated event or entity.
-
B.
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.
-
C.
hasWagerDuration
Indicates that a wager or bet is associated with a specific length of time for which it remains valid or in effect.
-
D.
simulcastsOn
Indicates that a broadcast (such as a TV or radio program) is transmitted simultaneously on the specified channel, platform, or service.
-
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_69f224b73d8c81908129383bfb397c87 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fb6fdc7eb081908ab8475efb38c430 |
completed | May 6, 2026, 4:44 p.m. |
| PD | Predicate disambiguation | batch_69fb5a986e588190b7a10892bd2ff44c |
completed | May 6, 2026, 3:13 p.m. |
Created at: April 29, 2026, 8:45 p.m.