Triple
T23340902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | La Sylphide |
E591730
|
entity |
| Predicate | costumeInnovation |
P96649
|
FINISHED |
| Object | popularization of the Romantic tutu |
—
|
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: popularization of the Romantic tutu | Statement: [La Sylphide, costumeInnovation, popularization of the Romantic tutu]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costumeInnovation Context triple: [La Sylphide, costumeInnovation, popularization of the Romantic tutu]
-
A.
costume
Indicates that one entity is wearing, dressed in, or outfitted with the other entity as a costume.
-
B.
costumeInspiration
chosen
Indicates that one entity serves as the creative source or model for another entity’s costume design.
-
C.
costumeFeatures
Indicates that a costume possesses or includes specific features, attributes, or decorative elements.
-
D.
costumeDesignEmphasisOn
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
-
E.
costumeElement
Indicates that one item functions as a component or part of another item's costume.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f198329d9c8190992627afa9b54bed |
completed | April 29, 2026, 5:33 a.m. |
| PD | Predicate disambiguation | batch_69effcfd8d288190937a887fe6023c11 |
completed | April 28, 2026, 12:19 a.m. |
Created at: April 17, 2026, 5:18 p.m.