Triple
T11731182
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ploom TECH |
E278899
|
entity |
| Predicate | designedAsAlternativeTo |
P5887
|
FINISHED |
| Object | traditional cigarettes |
—
|
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: traditional cigarettes | Statement: [Ploom TECH, designedAsAlternativeTo, traditional cigarettes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designedAsAlternativeTo Context triple: [Ploom TECH, designedAsAlternativeTo, traditional cigarettes]
-
A.
isAlternativeTo
chosen
Indicates that one entity can serve as a substitute or different option in place of another.
-
B.
alternativeUsedBy
Indicates that one entity serves as an alternative option or substitute that is used in place of another entity.
-
C.
discontinuedInFavorOf
Indicates that one thing has been stopped, ended, or phased out specifically so it can be replaced by another preferred alternative.
-
D.
usedInsteadOf
Indicates that one entity is employed or chosen as a substitute or replacement for another entity.
-
E.
replacedInNewDesignsBy
Indicates that an element or component is superseded and functionally taken over by another element or component in newer designs.
- 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.