Triple

T13761496
Position Surface form Disambiguated ID Type / Status
Subject Ancient Roman nomen E330619 entity
Predicate example P1259 FINISHED
Object Aemilius E345645 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: Aemilius | Statement: [Ancient Roman nomen, example, Aemilius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aemilius
Context triple: [Ancient Roman nomen, example, Aemilius]
  • A. Aemilius chosen
    Aemilius is an ancient Roman family name (nomen) from which the French given name Émile ultimately derives.
  • B. Gnaeus Manlius Vulso
    Gnaeus Manlius Vulso was a Roman consul and general of the 2nd century BC, best known for leading a successful campaign in Asia Minor that expanded Roman influence in the region.
  • C. Sempronius
    Sempronius is a character in Joseph Addison's tragedy "Cato," typically portrayed as a Roman senator whose ambition and intrigue drive much of the play's political tension.
  • D. Aulus
    Aulus is a common Roman praenomen (given name) frequently used among men in ancient Rome.
  • E. Lucius Aemilius Regillus
    Lucius Aemilius Regillus was a Roman admiral and statesman of the patrician Aemilia family, best known for his naval victories during the Roman–Seleucid War in the early 2nd century BC.
  • 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_69d81c573f288190aa2403d484fa3d49 completed April 9, 2026, 9:38 p.m.
NER Named-entity recognition batch_69de02250f4881908d5193b3d5d25844 completed April 14, 2026, 9 a.m.
NED1 Entity disambiguation (via context triple) batch_69f7a8606dbc8190b0f7c38583986141 completed May 3, 2026, 7:56 p.m.
Created at: April 9, 2026, 10:09 p.m.