Triple
T10005234
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Obsession (fragrance) |
E198223
|
entity |
| Predicate | eraAssociation |
P2830
|
FINISHED |
| Object | 1980s power fragrances |
—
|
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: 1980s power fragrances | Statement: [Obsession (fragrance), eraAssociation, 1980s power fragrances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eraAssociation Context triple: [Obsession (fragrance), eraAssociation, 1980s power fragrances]
-
A.
associatedConfederation
Indicates a relationship where an entity is linked to, belongs to, or is formally connected with a specific confederation.
-
B.
isAssociatedWith
chosen
Indicates that there exists a connection, relationship, or involvement between two entities without specifying its exact nature.
-
C.
divisionAssociation
Indicates an organizational relationship where one entity functions as a division, branch, or sub-unit of another entity.
-
D.
elementalAssociation
Indicates an association where one entity is linked or related to a particular element or elemental property (such as fire, water, earth, or air).
-
E.
associatedConsort
Indicates a spousal or consort relationship linking one entity to another as their partner.
- 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_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. |
Created at: March 30, 2026, 8:51 p.m.