Triple
T27139165
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Evie |
E681768
|
entity |
| Predicate | designsClothesFor |
P178771
|
FINISHED |
| Object | Auradon characters |
—
|
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: Auradon characters | Statement: [Evie, designsClothesFor, Auradon characters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designsClothesFor Context triple: [Evie, designsClothesFor, Auradon characters]
-
A.
fashionFunction
Indicates a relationship where something serves a particular role, purpose, or use within the context of fashion (such as aesthetic, practical, cultural, or symbolic function).
-
B.
fashionItem
Indicates that one entity is a fashion-related product or accessory associated with, used by, or worn by another entity.
-
C.
garmentType
Indicates the specific kind or category of garment associated with an entity.
-
D.
bodyDesigner
Indicates that one entity is responsible for designing, shaping, or creating the physical form or structure of another entity.
-
E.
costumeDesignEmphasisOn
Indicates that a costume design places particular focus or priority on a specified element, style, feature, or thematic aspect.
- 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_69eefacca3888190b67238d380e8f28b |
completed | April 27, 2026, 5:57 a.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
| PDg | Predicate description generation | batch_69f71421e8d08190807ccfb15d0f0ddb |
completed | May 3, 2026, 9:23 a.m. |
Created at: April 27, 2026, 9:08 a.m.