Triple
T37676949
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Maxx |
E938120
|
entity |
| Predicate | hasProtagonistWithAlterEgo |
P19776
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Maxx, hasProtagonistWithAlterEgo, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasProtagonistWithAlterEgo Context triple: [The Maxx, hasProtagonistWithAlterEgo, true]
-
A.
hasFictionalAlterEgoOf
Indicates that one entity is the fictional alter ego, persona, or alternate identity of another entity.
-
B.
protagonistAlterEgoOf
chosen
Indicates that one entity is the alternate identity or secret persona of the main character (protagonist) in a narrative.
-
C.
antagonistAlterEgoOf
Indicates that one entity serves as the primary opposing force or enemy of another entity’s alternate identity or secret persona.
-
D.
hasAlternateHero
Indicates that an entity is associated with a different or substitute hero that can take its place or serve as an alternative.
-
E.
hasSecondaryProtagonist
Indicates that an entity (such as a work of fiction) features another character who serves as a secondary or supporting main protagonist alongside the primary one.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a1772e48190ba738c6d11b321e2 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:18 p.m.