Triple
T32866474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Savior Complex |
E840661
|
entity |
| Predicate | mainCharacterAlignment |
P22459
|
FINISHED |
| Object | antihero |
—
|
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: antihero | Statement: [Savior Complex, mainCharacterAlignment, antihero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainCharacterAlignment Context triple: [Savior Complex, mainCharacterAlignment, antihero]
-
A.
characterAlignment
chosen
Indicates the moral or ethical stance a character holds, typically along axes such as good–evil and lawful–chaotic.
-
B.
primaryRaceAlignment
Indicates how an entity’s main racial identity or classification is aligned, categorized, or associated within a defined racial framework or system.
-
C.
mainMortalCharacter
Indicates that the referenced entity serves as the primary mortal (non-immortal) character in the context of a story or narrative.
-
D.
mainCharacterField
Indicates that one entity is designated as the primary or central character associated with another entity, such as a work or narrative.
-
E.
mainProtagonist
Indicates that the subject is the central character or primary focus in the narrative of the related work.
- 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_69f34942465c819099b3fb47f9044f58 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fcc4b700748190ae00b21d09c96695 |
completed | May 7, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69fcb0f9d3d881908a049475182fb039 |
completed | May 7, 2026, 3:34 p.m. |
Created at: May 1, 2026, 1:17 a.m.