Triple

T15220104
Position Surface form Disambiguated ID Type / Status
Subject Tiberius Gemellus E363742 entity
Predicate relative P37 FINISHED
Object Claudius E6391 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: Claudius | Statement: [Tiberius Gemellus, relative, Claudius]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Claudius
Context triple: [Tiberius Gemellus, relative, Claudius]
  • A. Claudius chosen
    Claudius is a masculine given name of ancient Roman origin, famously borne by several Roman emperors and historical figures.
  • B. Claudi
    Claudi is a given name, typically a variant or shortened form of names like Claudiu or Claudia used in various European languages.
  • C. Tiberius Claudius Caesar Britannicus
    Tiberius Claudius Caesar Britannicus was the son of the Roman emperor Claudius and his third wife Messalina, and a briefly prominent imperial heir whose position was eclipsed by Nero.
  • D. Tiberius
    Tiberius was a Byzantine emperor associated with the ruling House of Heraclius during the early medieval period.
  • 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_69d85a0ce24c81909c4d3b6475548c95 completed April 10, 2026, 2:01 a.m.
NER Named-entity recognition batch_69e007709d3881908384f0fe1e0218d0 completed April 15, 2026, 9:47 p.m.
NED1 Entity disambiguation (via context triple) batch_69fef88f8ac881908ca32de44b5aa53a completed May 9, 2026, 9:04 a.m.
Created at: April 10, 2026, 3:11 a.m.