Triple
T26310921
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libre Hair Mist |
E661816
|
entity |
| Predicate | hasTopNotesSimilarTo |
P39617
|
FINISHED |
| Object | orange blossom |
—
|
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: orange blossom | Statement: [Libre Hair Mist, hasTopNotesSimilarTo, orange blossom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTopNotesSimilarTo Context triple: [Libre Hair Mist, hasTopNotesSimilarTo, orange blossom]
-
A.
hasBaseNotesSimilarTo
Indicates that one entity has base notes that are similar in scent profile or composition to those of another entity.
-
B.
hasMusicalStyleSimilarTo
Indicates that two entities share a comparable or closely related musical style or sound.
-
C.
hasNotableMelodicSimilarityTo
Indicates that one musical piece shares a clearly recognizable and significant similarity in melody with another.
-
D.
topNote
chosen
Indicates that one entity serves as the primary or highest-level note associated with another entity.
-
E.
notableFlavorNotes
Indicates that something is characterized by specific, distinguishable flavor notes that are especially prominent or noteworthy.
- 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_69f676c440708190a4b9974e95d2291a |
completed | May 2, 2026, 10:12 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 26, 2026, 10:22 p.m.