Triple
T26657473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Strawberry Fields |
E666546
|
entity |
| Predicate | costumeDesignHighlight |
P90245
|
FINISHED |
| Object | blue cocktail dress |
—
|
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: blue cocktail dress | Statement: [Strawberry Fields, costumeDesignHighlight, blue cocktail dress]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costumeDesignHighlight Context triple: [Strawberry Fields, costumeDesignHighlight, blue cocktail dress]
-
A.
costumeDesignEmphasisOn
chosen
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
-
B.
costumeDesignNotability
Indicates that an entity is notable or recognized specifically for its work or achievements in costume design.
-
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.
costumeFeatures
Indicates that a costume possesses or includes specific features, attributes, or decorative elements.
- 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_69ee9cf8c7188190b9b00270a8a89164 |
completed | April 26, 2026, 11:17 p.m. |
| NER | Named-entity recognition | batch_69f616bb8574819087339f6e25346d2c |
completed | May 2, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69f60b8bb0d08190ab5a9a2a8847c6f4 |
completed | May 2, 2026, 2:34 p.m. |
Created at: April 27, 2026, 2:35 a.m.