Triple

T14670167
Position Surface form Disambiguated ID Type / Status
Subject Gaius Calpurnius Piso E344488 entity
Predicate opponent P437 FINISHED
Object Nero E12097 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: Nero | Statement: [Gaius Calpurnius Piso, opponent, Nero]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nero
Context triple: [Gaius Calpurnius Piso, opponent, Nero]
  • A. Nero
    Nero is one of Madame Medusa’s pet alligators and henchmen in Disney’s animated film “The Rescuers.”
  • B. Nero
    Nero is the vengeful Romulan miner who serves as the primary antagonist in the 2009 Star Trek film reboot.
  • C. Nero chosen
    Nero was a 1st-century Roman emperor best known for his tyrannical rule, persecution of Christians, and association with the Great Fire of Rome.
  • D. Nero Julius Caesar
    Nero Julius Caesar was the eldest son of the Roman emperor Vespasian and an early heir of the Flavian dynasty who died before he could claim the throne.
  • E. Caligula
    Caligula was a first-century Roman emperor infamous for his autocratic rule, extravagance, and accounts of cruelty and madness.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

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_69d822e283fc8190a0e4c235cf880052 completed April 9, 2026, 10:06 p.m.
NER Named-entity recognition batch_69deb54ef2908190b189ced65eec434a completed April 14, 2026, 9:44 p.m.
NED1 Entity disambiguation (via context triple) batch_69fdf07c7fa88190bb09f2f444d69786 completed May 8, 2026, 2:17 p.m.
Created at: April 10, 2026, 1:27 a.m.