Triple

T31916927
Position Surface form Disambiguated ID Type / Status
Subject Lucius Scribonius Libo (consul 16 AD) E814856 entity
Predicate succeeded by (as consul) P113234 FINISHED
Object consuls of 17 AD LITERAL 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: consuls of 17 AD | Statement: [Lucius Scribonius Libo (consul 16 AD), succeeded by (as consul), consuls of 17 AD]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: succeeded by (as consul)
Context triple: [Lucius Scribonius Libo (consul 16 AD), succeeded by (as consul), consuls of 17 AD]
  • A. succeededInConsulshipBy chosen
    Indicates that one individual’s term in the consulship was immediately followed by another individual’s term in the same office.
  • B. precededInConsulshipBy
    Indicates that one consul’s term of office occurred immediately before another consul’s term.
  • C. succeededByAsLieutenantGovernor
    Indicates that one individual was followed in office by another individual specifically in the role of lieutenant governor.
  • D. successorAsPraetorianPrefect
    Indicates that one individual assumed the office of Praetorian Prefect directly after another, serving as that predecessor’s successor in the role.
  • E. succeededByEmperor
    Indicates that one emperor directly followed another emperor in succession.
  • F. None of above.

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_69f348f109d88190b5005372c53d2fcd completed April 30, 2026, 12:20 p.m.
NER Named-entity recognition batch_69ff1c91bbac8190b84012dee1cb3b2c completed May 9, 2026, 11:37 a.m.
PD Predicate disambiguation batch_69ff1c23ca508190bb5a435d765b7e53 completed May 9, 2026, 11:36 a.m.
Created at: May 1, 2026, 12:02 a.m.