Triple
T37793373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HEETS |
E942140
|
entity |
| Predicate | regulatoryWarning |
P74619
|
FINISHED |
| Object | nicotine is addictive |
—
|
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: nicotine is addictive | Statement: [HEETS, regulatoryWarning, nicotine is addictive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regulatoryWarning Context triple: [HEETS, regulatoryWarning, nicotine is addictive]
-
A.
regulatoryIssues
Indicates that there are regulatory concerns, non-compliance, or potential violations associated with the related entity or activity.
-
B.
regulationAtIssue
Indicates that a specific regulation is the subject of concern, dispute, or analysis in the given context.
-
C.
regulatoryClarification
Indicates that an authority provides additional explanation or detail to resolve ambiguity or uncertainty in existing regulations or rules.
-
D.
regulatoryDescription
Indicates that a regulatory authority provides an official description or characterization of a rule, requirement, or compliance condition related to an entity or activity.
-
E.
hasHealthWarningOnPackaging
chosen
Indicates that an item’s packaging displays a health-related warning message or symbol.
- 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_69f76ee6f1f4819091e2cf9c9e6aee19 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fe12a899d4819080d48423f32eace9 |
completed | May 8, 2026, 4:43 p.m. |
| PD | Predicate disambiguation | batch_69fe0d7f6aa08190a1d2dfc025d4e0dc |
completed | May 8, 2026, 4:21 p.m. |
Created at: May 3, 2026, 4:19 p.m.