Triple
T21809723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iris gourmand accord |
E538438
|
entity |
| Predicate | trendAssociation |
P65488
|
FINISHED |
| Object | modern gourmand perfumery |
—
|
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: modern gourmand perfumery | Statement: [iris gourmand accord, trendAssociation, modern gourmand perfumery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: trendAssociation Context triple: [iris gourmand accord, trendAssociation, modern gourmand perfumery]
-
A.
hasTrend
Indicates that something exhibits or is associated with a particular pattern of change or direction over time.
-
B.
trends
Indicates that one entity exhibits a general direction of change or development over time in relation to another reference or context.
-
C.
associatedKeyword
chosen
Indicates that one entity is linked to or characterized by a particular keyword used for identification, categorization, or retrieval.
-
D.
associatedDanceTrend
Indicates a relationship where one entity is linked to, or commonly recognized as having, a particular dance trend connected with it.
-
E.
trendy
Indicates that something is currently fashionable, popular, or in line with prevailing styles or tastes.
- 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_69e0c473f0f8819086c9d1b4a143bd67 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f07cc4809c8190853e2777a1f573d4 |
completed | April 28, 2026, 9:24 a.m. |
| PD | Predicate disambiguation | batch_69e6be815a108190be81d7c987d0c0d6 |
completed | April 21, 2026, 12:02 a.m. |
Created at: April 16, 2026, 6:53 p.m.