Triple
T9841868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newport 100s |
E239245
|
entity |
| Predicate | hasCombustionType |
P31578
|
FINISHED |
| Object | combustible cigarette |
—
|
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: combustible cigarette | Statement: [Newport 100s, hasCombustionType, combustible cigarette]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCombustionType Context triple: [Newport 100s, hasCombustionType, combustible cigarette]
-
A.
combustionType
chosen
Indicates the specific manner or category of combustion process by which something burns or reacts chemically with an oxidizer.
-
B.
isCombustible
Indicates that a substance or material is capable of catching fire and burning under certain conditions.
-
C.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
-
D.
hasMotivePowerType
Indicates that an entity (such as a vehicle or machine) operates using a specified type of motive power (e.g., electric, diesel, steam).
-
E.
exhaustType
Indicates the specific kind or configuration of exhaust system associated with an 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_69ca84e3f0c48190ada72a65ebd50efd |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cdb34e3420819084bb31170e643cd0 |
completed | April 2, 2026, 12:07 a.m. |
| PD | Predicate disambiguation | batch_69cd03e57cac8190914bb5ae608a6e0e |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:33 p.m.