Triple
T26810036
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | White Diamonds fragrance line |
E671962
|
entity |
| Predicate | baseNotesInclude |
P91528
|
FINISHED |
| Object | musk |
—
|
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: musk | Statement: [White Diamonds fragrance line, baseNotesInclude, musk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: baseNotesInclude Context triple: [White Diamonds fragrance line, baseNotesInclude, musk]
-
A.
baseNotes
chosen
Indicates the fundamental or underlying elements, tones, or components that serve as the primary basis for something.
-
B.
baseNote
Indicates that one entity serves as the fundamental or reference note upon which another musical element (such as a chord, scale, or interval) is built or defined.
-
C.
heartNotesInclude
Indicates that one entity’s heart-related notes contain or encompass the other entity as part of their recorded content.
-
D.
supportsNotes
Indicates that one entity provides the capability for creating, storing, or handling notes associated with another entity.
-
E.
isNotedOn
Indicates that information about one entity is recorded, mentioned, or annotated on another entity (such as a document, record, or medium).
- 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_69eeb3225a3c8190aaf6746efeded2f3 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f61a2309508190b88c47908660c015 |
completed | May 2, 2026, 3:37 p.m. |
| PD | Predicate disambiguation | batch_69f611ad2eb48190ac1ed0090f13f7a9 |
completed | May 2, 2026, 3:01 p.m. |
Created at: April 27, 2026, 4:28 a.m.