Triple

T611040
Position Surface form Disambiguated ID Type / Status
Subject Nero E12097 entity
Predicate cognomen P6662 FINISHED
Object Ahenobarbus E76685 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: Ahenobarbus | Statement: [Nero, cognomen, Ahenobarbus]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Ahenobarbus
Context triple: [Nero, cognomen, Ahenobarbus]
  • A. Ahenobarbus chosen
    Ahenobarbus was the cognomen of a prominent Roman aristocratic family line to which the emperor Nero belonged.
  • B. Xoraxane Roma
    Xoraxane Roma are a subgroup of the Romani people traditionally associated with Muslim cultural and religious influences, particularly in the Balkans and parts of Eastern Europe.
  • C. Sicel
    Sicel was an ancient Indo-European language once spoken by the Sicel people in eastern Sicily before the dominance of Latin and Greek in the region.
  • D. Stilicho
    Stilicho was a prominent late Roman general and statesman of Vandal descent who effectively ruled the Western Roman Empire as regent during the reign of Emperor Honorius.
  • E. Ulpius
    Ulpius is the family name (nomen gentilicium) of the Roman emperor Trajan, identifying him as a member of the gens Ulpia.
  • 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_69a493309df48190a327f748e88049a6 completed March 1, 2026, 7:27 p.m.
NER Named-entity recognition batch_69a49df7c088819082eb70de4f0f4fbf completed March 1, 2026, 8:13 p.m.
NED1 Entity disambiguation (via context triple) batch_69a5554937a081909967f5298dbe1082 completed March 2, 2026, 9:15 a.m.
Created at: March 1, 2026, 7:35 p.m.