Triple
T26310891
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libre Le Parfum |
E661815
|
entity |
| Predicate | fragranceType |
P162359
|
FINISHED |
| Object | designer fragrance |
—
|
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: designer fragrance | Statement: [Libre Le Parfum, fragranceType, designer fragrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fragranceType Context triple: [Libre Le Parfum, fragranceType, designer fragrance]
-
A.
hasFragrance
Indicates that one entity possesses or emits a particular scent or aroma associated with another entity.
-
B.
fragranceInspiration
Indicates that one entity serves as the creative or conceptual inspiration behind the fragrance of another entity.
-
C.
hasFragranceForm
chosen
Indicates that an entity has a specific form or type of fragrance it is associated with or presented in.
-
D.
scentPositioning
Indicates the spatial placement or arrangement of a scent relative to other objects, locations, or reference points.
-
E.
olfactoryFamily
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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f62d53ad58819080c5227c7a729d15 |
completed | May 2, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69f62c15952881908a5ea0c25904afec |
completed | May 2, 2026, 4:53 p.m. |
Created at: April 26, 2026, 10:22 p.m.