Triple
T2692704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lucky Strike |
E58439
|
entity |
| Predicate | hasAddictiveSubstance |
P41092
|
FINISHED |
| Object | nicotine |
—
|
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 | Statement: [Lucky Strike, hasAddictiveSubstance, nicotine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAddictiveSubstance Context triple: [Lucky Strike, hasAddictiveSubstance, nicotine]
-
A.
hasAddictionPotential
Indicates that one entity (typically a substance or activity) has the capacity to cause another entity (typically a person) to develop dependence or addictive behavior toward it.
-
B.
addiction
Indicates a compulsive dependence of one entity on a substance, activity, or behavior, typically despite negative consequences and difficulty stopping.
-
C.
hasNotableDrug
Indicates that an entity is associated with a drug that is considered notable or significant in some recognized context.
-
D.
usesDrug
Indicates that an entity consumes, administers, or otherwise makes use of a specified drug.
-
E.
drugPolicy
Indicates the rules, regulations, or guidelines governing the use, control, or management of drugs within a given context.
- 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_69ab4ac269e481909cb317d79e68b75b |
completed | March 6, 2026, 9:44 p.m. |
| NER | Named-entity recognition | batch_69abda0dd97c81909a60cf200f57c087 |
completed | March 7, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69abd81ea5d88190ab5c8f8b8064b931 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd879bb808190bd2c34de1664c816 |
completed | March 7, 2026, 7:49 a.m. |
Created at: March 6, 2026, 9:54 p.m.