Triple

T27692896
Position Surface form Disambiguated ID Type / Status
Subject Oregon Lottery E698203 entity
Predicate hasResponsibleGamblingPolicy P198515 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: [Oregon Lottery, hasResponsibleGamblingPolicy, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasResponsibleGamblingPolicy
Context triple: [Oregon Lottery, hasResponsibleGamblingPolicy, yes]
  • A. hasResponsibleGamblingProgram
    Indicates that an entity has implemented and maintains a program or measures aimed at promoting responsible gambling practices.
  • B. hasResponsibleGamingMessage
    Indicates that an entity includes or is associated with a message promoting responsible or safe participation in gaming or gambling activities.
  • C. hasResponsibleGamblingPartnership
    Indicates that an entity maintains a formal partnership or collaboration focused on promoting or supporting responsible gambling practices.
  • D. hasGamingLicenseJurisdiction
    Indicates that an entity holds legal authority or permission to conduct gaming activities within a specified jurisdiction.
  • E. hasCasino
    Indicates that an entity includes, contains, or is associated with a casino facility or gambling establishment.
  • F. None of above. chosen

Provenance (4 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_69ef590df8708190af5488f0638e790c completed April 27, 2026, 12:39 p.m.
NER Named-entity recognition batch_69fef112398081909237c3872345968b completed May 9, 2026, 8:32 a.m.
PD Predicate disambiguation batch_69feefb14ec08190ab401987d8c84a23 completed May 9, 2026, 8:26 a.m.
PDg Predicate description generation batch_69fef1112b0c8190a8eb027edb71e4e0 completed May 9, 2026, 8:32 a.m.
Created at: April 27, 2026, 2:52 p.m.