Triple
T25003940
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hyalu B5 Serum |
E625788
|
entity |
| Predicate | fragranceStatus |
P23045
|
FINISHED |
| Object | contains 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: contains fragrance | Statement: [Hyalu B5 Serum, fragranceStatus, contains fragrance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fragranceStatus Context triple: [Hyalu B5 Serum, fragranceStatus, contains fragrance]
-
A.
hasFragrance
chosen
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.
launchedPerfume
Indicates that an entity has introduced or released a perfume product to the market.
-
D.
hasFragranceLine
Indicates that one entity (typically a brand or company) offers or is associated with a particular line or collection of fragrances.
-
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_69e2ff26c50481908bc82e799c9e6587 |
completed | April 18, 2026, 3:48 a.m. |
| NER | Named-entity recognition | batch_69f44b0ee0388190a07b6c0bcd817af9 |
completed | May 1, 2026, 6:41 a.m. |
| PD | Predicate disambiguation | batch_69f442c0c2e88190acd7f170f10ccef6 |
completed | May 1, 2026, 6:05 a.m. |
Created at: April 18, 2026, 6:05 a.m.