Triple

T16177496
Position Surface form Disambiguated ID Type / Status
Subject Aelia family E392601 entity
Predicate hasMember P10 FINISHED
Object Aelius Caesar E292689 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: Aelius Caesar | Statement: [Aelia family, hasMember, Aelius Caesar]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Aelius Caesar
Context triple: [Aelia family, hasMember, Aelius Caesar]
  • A. Lucius Caesar
    Lucius Caesar was the grandson and adopted son of the Roman emperor Augustus, groomed as a potential heir before his premature death in 2 AD.
  • B. Lucius Aelius Caesar chosen
    Lucius Aelius Caesar was a Roman senator and heir adopted by Emperor Hadrian, best known as the father of future co-emperor Lucius Verus.
  • C. Lucilius Bassus
    Lucilius Bassus was a 1st-century Roman general who played a key role in suppressing the Jewish Revolt under Emperor Vespasian.
  • D. Domitius
    Domitius is a Roman nomen (family name) associated with the ancient plebeian gens Domitia.
  • E. Vespasius
    Vespasius is the Latin nomen (family name) of the ancient Roman Vespasii family, from which the emperor Vespasian descended.
  • 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_69d87f1d32208190942e4e499a80c18c completed April 10, 2026, 4:39 a.m.
NER Named-entity recognition batch_69e22059e7048190b4592cb1516b5f8d completed April 17, 2026, 11:58 a.m.
NED1 Entity disambiguation (via context triple) batch_69fffefe4dc08190a6cc43a448ae6554 completed May 10, 2026, 3:43 a.m.
Created at: April 10, 2026, 5:02 a.m.