Triple
T23045059
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Altaira Morbius |
E573853
|
entity |
| Predicate | costumeNotability |
P150772
|
FINISHED |
| Object | short futuristic dresses |
—
|
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: short futuristic dresses | Statement: [Altaira Morbius, costumeNotability, short futuristic dresses]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: costumeNotability Context triple: [Altaira Morbius, costumeNotability, short futuristic dresses]
-
A.
costumeDesignNotability
Indicates that an entity is notable or recognized specifically for its work or achievements in costume design.
-
B.
costume
Indicates that one entity is wearing, dressed in, or outfitted with the other entity as a costume.
-
C.
costumeContext
Indicates the situational or narrative context in which a costume is used, such as the event, setting, or role it is associated with.
-
D.
costumeDesignEmphasisOn
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
-
E.
costumeType
Indicates the specific kind or category of costume associated with an entity.
- 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_69e245b9c11481909d06c872214d21af |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1851811e08190a5af6a112687327e |
completed | April 29, 2026, 4:12 a.m. |
| PD | Predicate disambiguation | batch_69ef89d5f71881908b9f9d0c8aab278c |
completed | April 27, 2026, 4:07 p.m. |
| PDg | Predicate description generation | batch_69ef9b7494f4819088ae59ea3d0ae8ab |
completed | April 27, 2026, 5:23 p.m. |
Created at: April 17, 2026, 3:54 p.m.