Triple
T31530418
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alberto Beddini |
E804461
|
entity |
| Predicate | costumeDesignContext |
P69136
|
FINISHED |
| Object | high fashion |
—
|
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: high fashion | Statement: [Alberto Beddini, costumeDesignContext, high fashion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costumeDesignContext Context triple: [Alberto Beddini, costumeDesignContext, high fashion]
-
A.
costumeDesignEmphasisOn
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
-
B.
costumeContext
chosen
Indicates the situational or narrative context in which a costume is used, such as the event, setting, or role it is associated with.
-
C.
costumeDesignStyle
Indicates the stylistic approach or aesthetic characteristics used in designing a costume for a character or production.
-
D.
costumeDesignerOfWork
Indicates that an entity serves as the costume designer responsible for the costumes in a particular creative work.
-
E.
designedCostumesFor
Indicates that one entity created or planned the costumes used by another entity, typically for a performance, production, or event.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a916d2e08190bafc01cba73b6469 |
completed | May 3, 2026, 1:47 a.m. |
| PD | Predicate disambiguation | batch_69f6a7548eb48190a69b60a3c6ad53b9 |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 30, 2026, 10:01 p.m.