Triple

T543629
Position Surface form Disambiguated ID Type / Status
Subject Vespasian E12684 entity
Predicate cognomen P6662 FINISHED
Object Vespasianus E12684 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: Vespasianus | Statement: [Vespasian, cognomen, Vespasianus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Vespasianus
Context triple: [Vespasian, cognomen, Vespasianus]
  • A. Vespasian chosen
    Vespasian was a 1st-century Roman emperor best known for restoring stability after Nero’s reign and initiating major building projects such as the Colosseum.
  • B. Domitian
    Domitian was a Roman emperor of the Flavian dynasty who ruled from 81 to 96 AD and is known for his authoritarian reign, extensive building projects in Rome, and eventual assassination.
  • C. Claudiianus
    Claudiianus is a Latin-derived personal name likely associated with or stemming from the Roman family name Claudius.
  • D. Claudius Pompeianus
    Claudius Pompeianus was a prominent 2nd-century Roman general and senator, son-in-law of Emperor Marcus Aurelius, who played a key military role during the Marcomannic Wars.
  • E. Tiberius
    Tiberius was the second Roman emperor, ruling from AD 14 to 37, known for his capable early administration and later reclusive, often harsh governance.
  • 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_69a49334226c81908b0ea1689ef6aa3f completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a498dea88881908a938fe8f2313bec completed March 1, 2026, 7:51 p.m.
NED1 Entity disambiguation (via context triple) batch_69a51f31b5a88190b39b678229ce83a3 completed March 2, 2026, 5:25 a.m.
Created at: March 1, 2026, 7:32 p.m.