Triple
T11115663
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nicorette |
E262877
|
entity |
| Predicate | patchStrengthVariants |
P97027
|
FINISHED |
| Object | various mg per 16-hour patch |
—
|
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: various mg per 16-hour patch | Statement: [Nicorette, patchStrengthVariants, various mg per 16-hour patch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: patchStrengthVariants Context triple: [Nicorette, patchStrengthVariants, various mg per 16-hour patch]
-
A.
weakenedVariantsInclude
Indicates that a set of weakened or attenuated forms of something (e.g., a virus, argument, or feature) contains or encompasses the specified variant.
-
B.
affectsVariant
Indicates that one entity has an influence or impact on a specific variant or version of another entity.
-
C.
strengthensFrom
Indicates that one entity becomes stronger, more effective, or more intense as a result of influence, support, or input from another entity.
-
D.
exportVariantOf
Indicates that one entity is an exported version or externally released form derived from another, original entity.
-
E.
styleVariants
Indicates that an entity has alternative stylistic forms or versions related to it.
- 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_69d6aa9b46cc8190b19f9f0cc45bf322 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d79aa7254c8190abce35696ad2be03 |
completed | April 9, 2026, 12:25 p.m. |
| PD | Predicate disambiguation | batch_69d7441cf8188190b8095f622c923156 |
completed | April 9, 2026, 6:15 a.m. |
| PDg | Predicate description generation | batch_69d750cb26f48190a134614d0aa8e283 |
completed | April 9, 2026, 7:10 a.m. |
Created at: April 8, 2026, 9:27 p.m.