Triple

T24327922
Position Surface form Disambiguated ID Type / Status
Subject Lucilla (Gladiator) E613151 entity
Predicate blackmailedThrough P155737 FINISHED
Object her son Lucius 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: her son Lucius | Statement: [Lucilla (Gladiator), blackmailedThrough, her son Lucius]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: blackmailedThrough
Context triple: [Lucilla (Gladiator), blackmailedThrough, her son Lucius]
  • A. blackmailedFor
    Indicates that one entity coerces another into doing or not doing something by threatening to reveal damaging or sensitive information about them.
  • B. blackmails
    Indicates that one entity coerces another by threatening to reveal damaging or sensitive information unless specific demands are met.
  • C. hasBlackmailPlot
    Indicates that one entity possesses or is involved in a scheme to coerce another entity using compromising or threatening information.
  • D. ransom
    Indicates demanding payment or concessions in exchange for releasing a person, object, or information held under threat or coercion.
  • E. bribedBy
    Indicates that an entity has received a bribe from another entity, implying an exchange of value to influence the entity’s actions or decisions.
  • 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_69e2d7db6d5c819091194918157a7c1f completed April 18, 2026, 1:01 a.m.
NER Named-entity recognition batch_69f292eebf7081908ef50ef331ff88aa completed April 29, 2026, 11:23 p.m.
PD Predicate disambiguation batch_69f287ad30048190b3ad3613486f277f completed April 29, 2026, 10:35 p.m.
PDg Predicate description generation batch_69f28b7ff1808190870dfe9af789a1eb completed April 29, 2026, 10:51 p.m.
Created at: April 18, 2026, 1:54 a.m.