Triple
T30343865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | My Dress-Up Darling |
E771822
|
entity |
| Predicate | animationProducer |
P129279
|
FINISHED |
| Object | Aniplex |
—
|
NE NERFINISHED |
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: Aniplex | Statement: [My Dress-Up Darling, animationProducer, Aniplex]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: animationProducer Context triple: [My Dress-Up Darling, animationProducer, Aniplex]
-
A.
animationDirector
Indicates that one entity serves as the animation director responsible for overseeing and guiding the animation work of another entity.
-
B.
animationStudio
Indicates that one entity is an animation studio responsible for creating, producing, or animating the other entity.
-
C.
animeProducer
chosen
Indicates that one entity is the producer responsible for creating, financing, or overseeing the production of an anime work involving the other entity.
-
D.
animator
Indicates that one entity serves as the animator or creator of animated content for another entity or work.
-
E.
videoDesigner
Indicates a relationship where one entity is responsible for designing or creating the visual and structural elements of a video for another entity or project.
- 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f682065a548190bff089d7dafbf3ad |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:55 p.m.