Triple
T10005255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Escape (fragrance) |
E198224
|
entity |
| Predicate | heartNotes |
P91527
|
FINISHED |
| Object | jasmine |
—
|
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: jasmine | Statement: [Escape (fragrance), heartNotes, jasmine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heartNotes Context triple: [Escape (fragrance), heartNotes, jasmine]
-
A.
heartNote
Indicates that one entity records or expresses a heartfelt or emotionally significant note or message about another entity.
-
B.
heartPresence
Indicates the existence or presence of a heart in or associated with the referenced entity.
-
C.
feltIn
Indicates that a sensation, emotion, or effect is experienced within a particular location, context, or entity.
-
D.
lettersWrittenBetween
Indicates that letters have been written and exchanged between the two entities, reflecting a mutual correspondence.
-
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_69ca830fcca48190bbbd9b20c233835f |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cdcd157d9c8190b863e4264f9a48b1 |
completed | April 2, 2026, 1:57 a.m. |
| PD | Predicate disambiguation | batch_69cd1da2cf9081908a6c0eb5247d0bc2 |
completed | April 1, 2026, 1:29 p.m. |
| PDg | Predicate description generation | batch_69cd3584b2b4819096ff2625a7f5f1b5 |
completed | April 1, 2026, 3:11 p.m. |
Created at: March 30, 2026, 8:51 p.m.