Triple
T14116874
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Febreze |
E339795
|
entity |
| Predicate | hasFragranceCategory |
P10884
|
FINISHED |
| Object | floral scents |
—
|
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: floral scents | Statement: [Febreze, hasFragranceCategory, floral scents]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFragranceCategory Context triple: [Febreze, hasFragranceCategory, floral scents]
-
A.
hasFragrance
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
B.
hasFragranceLine
Indicates that one entity (typically a brand or company) offers or is associated with a particular line or collection of fragrances.
-
C.
fragranceInspiration
Indicates that one entity serves as the creative or conceptual inspiration behind the fragrance of another entity.
-
D.
aromaticOilsPresent
Indicates that aromatic oils are present in or associated with the specified entity or context.
-
E.
olfactoryFamily
chosen
Indicates a relationship where one entity belongs to, or is categorized within, a particular olfactory family or scent classification defined by the other 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de6010a03c81909f5f160f8d1fa8fa |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.