Triple
T26310836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Libre Eau de Toilette |
E661814
|
entity |
| Predicate | heartNotesInclude |
P160238
|
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 Eau de Toilette, heartNotesInclude, orange blossom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heartNotesInclude Context triple: [Libre Eau de Toilette, heartNotesInclude, orange blossom]
-
A.
heartNotes
Indicates that one entity records or associates special notes, comments, or annotations about another entity in a favored or highlighted manner.
-
B.
heartNote
Indicates that one entity records or expresses a heartfelt or emotionally significant note or message about another entity.
-
C.
baseNotes
Indicates the fundamental or underlying elements, tones, or components that serve as the primary basis for something.
-
D.
heartMaterial
Indicates that one entity is the material or substance that composes the heart of another entity.
-
E.
hasNotabilityNote
Indicates that there is an associated note or annotation explaining the significance, prominence, or special relevance of the subject.
- 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_69ee812dacfc81908484aade9120fba9 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60ee7e6348190951e6f9647f5555b |
completed | May 2, 2026, 2:49 p.m. |
| PD | Predicate disambiguation | batch_69f5f7ff548c8190a23e98c5e66e0bc7 |
completed | May 2, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69f5ffc6268c8190b63f6360ebadab73 |
completed | May 2, 2026, 1:44 p.m. |
Created at: April 26, 2026, 10:22 p.m.