Triple
T27791822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Atmosphere |
E701099
|
entity |
| Predicate | hasProductBenefit |
P2188
|
FINISHED |
| Object | removal of dust |
—
|
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: removal of dust | Statement: [Atmosphere, hasProductBenefit, removal of dust]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProductBenefit Context triple: [Atmosphere, hasProductBenefit, removal of dust]
-
A.
hasBenefit
chosen
Indicates that one entity provides an advantage, improvement, or positive outcome to another entity.
-
B.
hasBenefitType
Indicates that an entity is associated with a specific category or type of benefit it provides or receives.
-
C.
benefitAppliesTo
Indicates that a particular benefit is applicable to, or valid for, a specified entity or context.
-
D.
hasBenefitDesign
Indicates that an entity possesses or is associated with a particular benefit-related design or configuration.
-
E.
benefitCharacteristic
Indicates that one entity possesses a quality or feature that provides an advantage, usefulness, or positive effect to 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_69ef6a50d8088190acbf3dfbb06d8091 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fe610e1f6881908f10070ba64643cf |
completed | May 8, 2026, 10:17 p.m. |
| PD | Predicate disambiguation | batch_69fe604c6c008190ad659e9b9fa82f7b |
completed | May 8, 2026, 10:14 p.m. |
Created at: April 27, 2026, 5:28 p.m.