Triple

T19744385
Position Surface form Disambiguated ID Type / Status
Subject Emil E474211 entity
Predicate hasEtymologicalOrigin P506 FINISHED
Object Aemilius NE NERFINISHED

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: [Emil, hasEtymologicalOrigin, Aemilius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aemilius
Context triple: [Emil, hasEtymologicalOrigin, 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. Attius Tullus Aufidius
    Attius Tullus Aufidius is a legendary Volscian leader and rival of the Roman general Coriolanus, best known from Plutarch’s writings and Shakespeare’s tragedy "Coriolanus."
  • E. Aulus
    Aulus is a common Roman praenomen (given name) frequently used among men in ancient Rome.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69d8e51940a0819087bd2996f98da668 completed April 10, 2026, 11:55 a.m.
NER Named-entity recognition batch_69e652923fd48190982c51c39814fd08 completed April 20, 2026, 4:21 p.m.
Created at: April 10, 2026, 1:47 p.m.