Triple
T11731022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Juul |
E278895
|
entity |
| Predicate | usageMethod |
P2529
|
FINISHED |
| Object | inhalation of aerosol vapor |
—
|
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: inhalation of aerosol vapor | Statement: [Juul, usageMethod, inhalation of aerosol vapor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usageMethod Context triple: [Juul, usageMethod, inhalation of aerosol vapor]
-
A.
usageInstruction
Indicates that one entity provides guidance or directions on how to properly use, operate, or handle another entity.
-
B.
usagePattern
Indicates how something is typically used or the recurring manner in which it is employed or consumed.
-
C.
usageType
chosen
Indicates the specific manner, purpose, or context in which something is used or intended to be used.
-
D.
errorUsage
Indicates that an error has occurred in how something is used, invoked, or applied within a given context.
-
E.
respondUsage
Indicates that one entity replies or reacts in some manner to the use or application of another entity.
- 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_69d6aaffec6881908bead509e8621742 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d8a4d94de08190a7184cf26d8cb94e |
completed | April 10, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69d88a7f51248190bf492bd7509b5413 |
completed | April 10, 2026, 5:28 a.m. |
Created at: April 8, 2026, 9:41 p.m.