Triple
T26310680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Opium Neon |
E661810
|
entity |
| Predicate | fragranceProfileComparedToOriginal |
P160565
|
FINISHED |
| Object | less dark than Black Opium |
—
|
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: less dark than Black Opium | Statement: [Black Opium Neon, fragranceProfileComparedToOriginal, less dark than Black Opium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fragranceProfileComparedToOriginal Context triple: [Black Opium Neon, fragranceProfileComparedToOriginal, less dark than Black Opium]
-
A.
fragranceProfileComparedToOriginal
chosen
Indicates how the fragrance profile of one item differs from or resembles that of the original version.
-
B.
hasFragrance
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
C.
fragranceInspiration
Indicates that one entity serves as the creative or conceptual inspiration behind the fragrance of another entity.
-
D.
launchedPerfume
Indicates that an entity has introduced or released a perfume product to the market.
-
E.
scentPositioning
Indicates the spatial placement or arrangement of a scent relative to other objects, locations, or reference points.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f612607c388190ab61d1ac7d18e08d |
completed | May 2, 2026, 3:04 p.m. |
| PD | Predicate disambiguation | batch_69f611a9272881909093360472be832c |
completed | May 2, 2026, 3 p.m. |
Created at: April 26, 2026, 10:22 p.m.