Triple
T31102097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Justice League film series |
E792700
|
entity |
| Predicate | overarchingAntagonist |
P67690
|
FINISHED |
| Object | Darkseid |
—
|
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: Darkseid | Statement: [Justice League film series, overarchingAntagonist, Darkseid]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: overarchingAntagonist Context triple: [Justice League film series, overarchingAntagonist, Darkseid]
-
A.
primaryAntagonistType
Indicates the role or category of the main opposing force or adversary that serves as the central source of conflict.
-
B.
isCentralAntagonist
chosen
Indicates that an entity serves as the primary opposing force or main villain driving conflict against the protagonist or central characters.
-
C.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
D.
leadAntagonistCharacter
Indicates that one character serves as the primary opposing or villainous force in relation to another entity in the narrative.
-
E.
antagonistBaseOf
Indicates that one entity serves as the primary base, headquarters, or stronghold from which an antagonist operates or exerts influence over another entity.
- 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_69f224cf157c81909e2d2bd88c9282c3 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:03 p.m.