Triple

T31337042
Position Surface form Disambiguated ID Type / Status
Subject The Adventure of Charles Augustus Milverton E799202 entity
Predicate nicknameOfAntagonist P171255 FINISHED
Object king of blackmailers 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: king of blackmailers | Statement: [The Adventure of Charles Augustus Milverton, nicknameOfAntagonist, king of blackmailers]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: nicknameOfAntagonist
Context triple: [The Adventure of Charles Augustus Milverton, nicknameOfAntagonist, king of blackmailers]
  • A. supervillainName
    Indicates that an entity is known by a particular supervillain name or alias.
  • B. leadAntagonistCharacter
    Indicates that one character serves as the primary opposing or villainous force in relation to another entity in the narrative.
  • C. mainAntagonistPortrayedBy
    Indicates that the person is the primary actor who plays the main antagonist character in a work.
  • D. fullyIntroducedAsAntagonistIn
    Indicates that an entity is completely and explicitly presented in a work as an antagonist within the specified context or narrative.
  • E. antagonistOccupation
    Indicates the role, job, or professional activity that the antagonist character performs.
  • F. None of above. chosen

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_69f224e3f6ac8190a13488516abca7c9 completed April 29, 2026, 3:33 p.m.
NER Named-entity recognition batch_69f69f11ba548190b8ad25fafb07b62b completed May 3, 2026, 1:04 a.m.
PD Predicate disambiguation batch_69f69d1d25e88190a7f57d323574da90 completed May 3, 2026, 12:55 a.m.
PDg Predicate description generation batch_69f69ea761848190acb31298e65b7892 completed May 3, 2026, 1:02 a.m.
Created at: April 29, 2026, 9:16 p.m.