Triple

T1686239
Position Surface form Disambiguated ID Type / Status
Subject Julio-Claudian dynasty E36447 entity
Predicate hasEmperor P10335 FINISHED
Object Caligula E10757 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: Caligula | Statement: [Julio-Claudian dynasty, hasEmperor, Caligula]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Caligula
Context triple: [Julio-Claudian dynasty, hasEmperor, Caligula]
  • A. Caligula chosen
    Caligula was a first-century Roman emperor infamous for his autocratic rule, extravagance, and accounts of cruelty and madness.
  • B. Nero
    Nero was a 1st-century Roman emperor best known for his tyrannical rule, persecution of Christians, and association with the Great Fire of Rome.
  • C. Nero
    Nero is the vengeful Romulan miner who serves as the primary antagonist in the 2009 Star Trek film reboot.
  • 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. Commodus
    Commodus was a Roman emperor (reigned 180–192 AD) known for his erratic rule, self-indulgence, and association with the decline of the Roman Empire.
  • 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_69a886151508819084fa7f1ce6e05577 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa6293c368819094ab0f615e418647 completed March 6, 2026, 5:13 a.m.
NED1 Entity disambiguation (via context triple) batch_69adb5b9be4481908c0b6f030889edfb completed March 8, 2026, 5:45 p.m.
Created at: March 4, 2026, 7:29 p.m.