Triple
T2522424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dolce & Gabbana The One |
E55552
|
entity |
| Predicate | useOccasion |
P37361
|
FINISHED |
| Object | evening wear |
—
|
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: evening wear | Statement: [Dolce & Gabbana The One, useOccasion, evening wear]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: useOccasion Context triple: [Dolce & Gabbana The One, useOccasion, evening wear]
-
A.
usedOnOccasions
chosen
Indicates that something is employed or utilized during specific events, times, or circumstances rather than continuously.
-
B.
displayOccasion
Indicates the event, context, or situation during which something is presented, shown, or made visible.
-
C.
servingOccasion
Indicates the occasion, event, or context during which something (typically food or drink) is served.
-
D.
primaryOccasion
Indicates that one occasion is the main or most significant event associated with a given context, entity, or activity.
-
E.
marksOccasion
Indicates that an event, action, or item serves to commemorate, celebrate, or formally recognize a particular occasion or milestone.
- 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_69ab49e4749c8190813311efd1630f1b |
completed | March 6, 2026, 9:40 p.m. |
| NER | Named-entity recognition | batch_69abd23895348190bb4dad6d7174893a |
completed | March 7, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_69abd0c144b0819092f32a13c1d127e5 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.