Triple

T11887731
Position Surface form Disambiguated ID Type / Status
Subject Licinius II E282830 entity
Predicate removedFromSuccession P102073 FINISHED
Object after defeat of Licinius I 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: after defeat of Licinius I | Statement: [Licinius II, removedFromSuccession, after defeat of Licinius I]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: removedFromSuccession
Context triple: [Licinius II, removedFromSuccession, after defeat of Licinius I]
  • A. removedFrom
    Indicates that one entity has been taken away, extracted, or detached from another entity or context.
  • B. removedFromPlaceOfHonor
    Indicates that an entity has been taken out of a previously held position of distinction, prestige, or special recognition in a particular context or location.
  • C. supportedSuccessionOf
    Indicates that one entity actively endorsed or helped bring about the transfer of power, position, or role from a predecessor to a successor.
  • D. removedOn
    Indicates that an entity was taken away, deleted, or detached at a specific point in time.
  • E. hasSuccession
    Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
  • F. None of above. chosen

Provenance (4 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_69d6ab2a90b08190a4e818821cc93e6d completed April 8, 2026, 7:23 p.m.
NER Named-entity recognition batch_69d8d3a13370819086386fecb99e4f0b completed April 10, 2026, 10:40 a.m.
PD Predicate disambiguation batch_69d8bb2fca4481909893f3428b0871ac completed April 10, 2026, 8:56 a.m.
PDg Predicate description generation batch_69d8d399d58c81908dab572aa82426d7 completed April 10, 2026, 10:40 a.m.
Created at: April 8, 2026, 9:44 p.m.