Triple
T26809999
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Black Pearls |
E671961
|
entity |
| Predicate | hasFragranceIndustry |
P163462
|
FINISHED |
| Object | fine fragrances |
—
|
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: fine fragrances | Statement: [Black Pearls, hasFragranceIndustry, fine fragrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFragranceIndustry Context triple: [Black Pearls, hasFragranceIndustry, fine fragrances]
-
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.
hasFragranceForm
Indicates that an entity has a specific form or type of fragrance it is associated with or presented in.
-
D.
fragranceInspiration
Indicates that one entity serves as the creative or conceptual inspiration behind the fragrance of another entity.
-
E.
aromaticOilsPresent
Indicates that aromatic oils are present in or associated with the specified entity or context.
- F. None of above. chosen
Provenance (4 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f638d11c988190af7fd4572b08e038 |
completed | May 2, 2026, 5:48 p.m. |
| PD | Predicate disambiguation | batch_69f63709e4848190b5cf322e06b23fb6 |
completed | May 2, 2026, 5:40 p.m. |
| PDg | Predicate description generation | batch_69f638344b148190bf0414ef7c5f1f38 |
completed | May 2, 2026, 5:45 p.m. |
Created at: April 27, 2026, 4:28 a.m.