Triple

T33385021
Position Surface form Disambiguated ID Type / Status
Subject Kodiak moist snuff E854888 entity
Predicate requiresWarningLabel P78373 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: [Kodiak moist snuff, requiresWarningLabel, yes]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: requiresWarningLabel
Context triple: [Kodiak moist snuff, requiresWarningLabel, yes]
  • A. warningLabelRequired chosen
    Indicates that an item, product, or situation must display a warning label to alert users to potential risks or hazards.
  • B. requiresCautionIn
    Indicates that engaging with or operating within the referenced context, situation, or environment demands heightened care, attention, or precaution.
  • C. hasHealthWarningOnPackaging
    Indicates that an item’s packaging displays a health-related warning message or symbol.
  • D. safetyLabel
    Indicates that an entity has been assigned a safety-related classification or warning status.
  • E. warnsAbout
    Indicates that one entity alerts or cautions another entity about a potential danger, risk, or problem.
  • 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_69f3496d54048190a1cb91fdd7caa6ea completed April 30, 2026, 12:22 p.m.
NER Named-entity recognition batch_69ff41645c548190b7cb4e53079b93ef completed May 9, 2026, 2:15 p.m.
PD Predicate disambiguation batch_69ff410aa33c8190869ba769ac2a93ce completed May 9, 2026, 2:13 p.m.
Created at: May 1, 2026, 1:35 a.m.