Triple

T2661349
Position Surface form Disambiguated ID Type / Status
Subject Claudian gens E54731 entity
Predicate producedEmperor P41257 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: [Claudian gens, producedEmperor, Nero]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Nero
Context triple: [Claudian gens, producedEmperor, Nero]
  • A. 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.
  • B. Nero
    Nero is the vengeful Romulan miner who serves as the primary antagonist in the 2009 Star Trek film reboot.
  • C. Caligula
    Caligula was a first-century Roman emperor infamous for his autocratic rule, extravagance, and accounts of cruelty and madness.
  • D. Galba
    Galba was a Roman general and statesman who briefly ruled as emperor during the tumultuous Year of the Four Emperors following Nero’s death.
  • E. Elagabalus
    Elagabalus was a Roman emperor of the Severan dynasty known for his short, tumultuous reign and controversial religious and social reforms.
  • 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_69ab49e028948190b97e01d73548b1d9 completed March 6, 2026, 9:40 p.m.
NER Named-entity recognition batch_69abdd1e80dc819083e04e1427d187d0 completed March 7, 2026, 8:09 a.m.
NED1 Entity disambiguation (via context triple) batch_69afbbb50cec8190aea067e486a5b092 completed March 10, 2026, 6:35 a.m.
Created at: March 6, 2026, 9:53 p.m.