Triple

T27810683
Position Surface form Disambiguated ID Type / Status
Subject Era of the First Order–Resistance conflict E702509 entity
Predicate hasPrimaryAntagonistFaction P67690 FINISHED
Object First Order 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: First Order | Statement: [Era of the First Order–Resistance conflict, hasPrimaryAntagonistFaction, First Order]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasPrimaryAntagonistFaction
Context triple: [Era of the First Order–Resistance conflict, hasPrimaryAntagonistFaction, First Order]
  • A. hasOpposingFaction
    Indicates that one faction stands in opposition or conflict to another faction.
  • B. hasAntagonistGroup
    Indicates that an entity is opposed or challenged by a specific group acting as its antagonist.
  • C. hasAntagonisticProtagonist
    Indicates that the work features a main character who opposes or undermines the typical heroic or moral expectations of a traditional protagonist.
  • D. antagonistOf
    Indicates a relationship where one entity actively opposes, conflicts with, or serves as an adversary to another.
  • E. isCentralAntagonist chosen
    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 (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_69ef840a16748190926719ab96120bae completed April 27, 2026, 3:43 p.m.
NER Named-entity recognition batch_69fe6739d4dc8190ae7505c089bbac29 completed May 8, 2026, 10:44 p.m.
PD Predicate disambiguation batch_69fe6541dffc81909c66a61ba69f38fc completed May 8, 2026, 10:35 p.m.
Created at: April 27, 2026, 5:42 p.m.