Triple
T11731348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | On! nicotine pouches |
E278902
|
entity |
| Predicate | combustionRequired |
P56321
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [On! nicotine pouches, combustionRequired, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: combustionRequired Context triple: [On! nicotine pouches, combustionRequired, false]
-
A.
combustionType
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
-
B.
combustionChamber
Indicates that one entity functions as the combustion chamber in which another entity’s fuel–air mixture is burned to produce energy or propulsion.
-
C.
combustionProperty
chosen
Indicates a relationship where an entity is characterized by how it behaves in combustion, such as its flammability, ignition conditions, or burning behavior.
-
D.
isCombustedBy
Indicates that something undergoes combustion as a result of an action or process performed by another agent or cause.
-
E.
isCombustible
Indicates that a substance or material is capable of catching fire and burning under certain conditions.
- 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.