Triple
T37468086
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bianca |
E931080
|
entity |
| Predicate | characterAlignmentChange |
P22459
|
FINISHED |
| Object | villain to hero |
—
|
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: villain to hero | Statement: [Bianca, characterAlignmentChange, villain to hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterAlignmentChange Context triple: [Bianca, characterAlignmentChange, villain to hero]
-
A.
characterAlignment
chosen
Indicates the moral or ethical stance a character holds, typically along axes such as good–evil and lawful–chaotic.
-
B.
protagonistTransformation
Indicates a change or evolution that the main character undergoes, typically altering their traits, beliefs, or role over the course of a narrative.
-
C.
characterArc
Indicates the developmental journey or transformation a character undergoes over the course of a narrative.
-
D.
characterArcElement
Indicates that one element is a component or stage within a character’s overall developmental arc or transformation.
-
E.
affectsCharacterArc
Indicates that one event, action, or element causes a meaningful change or development in a character’s personal journey or growth over the course of the story.
- 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_69f76ec2af148190897d101070d7f415 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fff4530f908190afe9387f732c2b7e |
completed | May 10, 2026, 2:58 a.m. |
| PD | Predicate disambiguation | batch_69fff3c01a64819091196875b0c88607 |
completed | May 10, 2026, 2:56 a.m. |
Created at: May 3, 2026, 4:17 p.m.