Triple
T26310740
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Le Parfum (Yves Saint Laurent Libre Le Parfum) |
E661812
|
entity |
| Predicate | fragranceLine |
P46923
|
FINISHED |
| Object | Yves Saint Laurent Libre |
—
|
NE NERFINISHED |
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: Yves Saint Laurent Libre | Statement: [Le Parfum (Yves Saint Laurent Libre Le Parfum), fragranceLine, Yves Saint Laurent Libre]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fragranceLine Context triple: [Le Parfum (Yves Saint Laurent Libre Le Parfum), fragranceLine, Yves Saint Laurent Libre]
-
A.
hasFragranceLine
chosen
Indicates that one entity (typically a brand or company) offers or is associated with a particular line or collection of fragrances.
-
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.
brandLine
Indicates that one brand is a specific product line or sub-brand offered under another brand.
- 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_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b3a8ae0819090189fbd8eb19f2f |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 26, 2026, 10:22 p.m.