Triple

T34918343
Position Surface form Disambiguated ID Type / Status
Subject Freehold Raceway E1007067 entity
Predicate hasPariMutuelWagering P47794 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: [Freehold Raceway, hasPariMutuelWagering, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPariMutuelWagering
Context triple: [Freehold Raceway, hasPariMutuelWagering, yes]
  • A. wageringAvailable
    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. hasSportsbook
    Indicates that an entity operates, offers, or is associated with a sportsbook service for placing sports bets.
  • D. hasToteBetting chosen
    Indicates that an entity offers or is associated with pari-mutuel (tote) betting services or facilities.
  • E. hasBetType
    Indicates that an entity is associated with or classified under a specific type or category of bet.
  • 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_69f76dc2b6b0819095a61debbd405269 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69ffacdf9f5c8190baef0245edfe87fc completed May 9, 2026, 9:53 p.m.
PD Predicate disambiguation batch_69ffac5e86e08190a1e6da0840a237ad completed May 9, 2026, 9:51 p.m.
Created at: May 3, 2026, 4 p.m.