Triple
T28969266
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Infinity Crusade |
E734225
|
entity |
| Predicate | antagonistGoal |
P108466
|
FINISHED |
| Object | impose universal good |
—
|
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: impose universal good | Statement: [Infinity Crusade, antagonistGoal, impose universal good]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: antagonistGoal Context triple: [Infinity Crusade, antagonistGoal, impose universal good]
-
A.
antagonistOf
Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
-
B.
missionOfAntagonist
chosen
Indicates the primary goal, plan, or objective that the antagonist is actively pursuing.
-
C.
antagonistActionOf
Indicates that one entity performs an action in opposition or hostility toward another entity, acting as its antagonist.
-
D.
antagonistStatus
Indicates that an entity holds an opposing or adversarial role, often acting as the main source of conflict relative to another entity or objective.
-
E.
hasAntagonisticProtagonist
Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65c3001908190a21cfe2d25c319eb |
completed | May 2, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:04 a.m.