Triple
T14918792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vitas |
E371452
|
entity |
| Predicate | knownForCostumes |
P116673
|
FINISHED |
| Object | elaborate stage costumes |
—
|
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: elaborate stage costumes | Statement: [Vitas, knownForCostumes, elaborate stage costumes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: knownForCostumes Context triple: [Vitas, knownForCostumes, elaborate stage costumes]
-
A.
designedCostumesFor
Indicates that one entity created or planned the costumes used by another entity, typically for a performance, production, or event.
-
B.
costumeDesignerOfWork
Indicates that an entity serves as the costume designer responsible for the costumes in a particular creative work.
-
C.
isCostumedCharacterFor
Indicates that one entity serves as a costumed character representation or mascot for another entity, typically for promotional or entertainment purposes.
-
D.
costumeDesignEmphasisOn
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
-
E.
costumeDesignNotability
Indicates that an entity is notable or recognized specifically for its work or achievements in costume design.
- F. None of above. chosen
Provenance (4 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_69d85cc7ea3481908228b5acb7d06f12 |
completed | April 10, 2026, 2:13 a.m. |
| NER | Named-entity recognition | batch_69ded62f76bc81909ebc8899096cd1a0 |
completed | April 15, 2026, 12:05 a.m. |
| PD | Predicate disambiguation | batch_69de9a52ba988190a26e268b4ea083ea |
completed | April 14, 2026, 7:49 p.m. |
| PDg | Predicate description generation | batch_69deb1a4d8dc8190a4c0841c20f2875f |
completed | April 14, 2026, 9:29 p.m. |
Created at: April 10, 2026, 2:33 a.m.