Triple

T37592083
Position Surface form Disambiguated ID Type / Status
Subject Alcarnus E935283 entity
Predicate primaryAntagonistPresence P81119 FINISHED
Object Maghda E2226595 NE 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: Maghda | Statement: [Alcarnus, primaryAntagonistPresence, Maghda]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryAntagonistPresence
Context triple: [Alcarnus, primaryAntagonistPresence, Maghda]
  • A. primaryAntagonists chosen
    Indicates that the referenced entities serve as the main opposing or adversarial forces in relation to a specified subject or narrative.
  • B. hasAntagonisticProtagonist
    Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
  • C. primaryAntagonistType
    Indicates the role or category of the main opposing force or adversary that serves as the central source of conflict.
  • 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. isCentralAntagonist
    Indicates that an entity serves as the primary opposing force or main villain driving conflict against the protagonist or central characters.
  • F. None of above.

Provenance (4 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_69f76ecf39c081909baffe597bb55273 completed May 3, 2026, 3:50 p.m.
NER Named-entity recognition batch_6a037c8efcd4819088c2aeead65d93df completed May 12, 2026, 7:16 p.m.
NED1 Entity disambiguation (via context triple) batch_6a40d665f2b081909d01d83c055d4116 completed June 28, 2026, 8:08 a.m.
PD Predicate disambiguation batch_6a037a1553e08190bb7424c448cb1f33 completed May 12, 2026, 7:05 p.m.
Created at: May 3, 2026, 4:18 p.m.