Triple

T1703818
Position Surface form Disambiguated ID Type / Status
Subject Rule of Four E36824 entity
Predicate successionPlan P545 FINISHED
Object Caesares succeed Augusti 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: Caesares succeed Augusti | Statement: [Rule of Four, successionPlan, Caesares succeed Augusti]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: successionPlan
Context triple: [Rule of Four, successionPlan, Caesares succeed Augusti]
  • A. successionOrder
    Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
  • B. successionOutcome
    Indicates the result or consequence of a succession event, such as who or what ultimately assumes a position, role, or status after a predecessor.
  • C. successionTrigger
    Indicates a condition or event that initiates or causes a transfer of position, role, or authority from one entity to another.
  • D. successionDefinedBy chosen
    Indicates that the rules, order, or conditions of succession for one entity are determined or specified by another entity.
  • E. successorDesignationFor
    Indicates the designation or identification of an entity that is intended to succeed or replace another entity in a given role, position, or function.
  • 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_69a88617439c819094ffb5d16a0f6307 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69ab75ad24408190814069e6e3ef9e59 completed March 7, 2026, 12:47 a.m.
PD Predicate disambiguation batch_69aa61bad17c8190861b92cfb423f68f completed March 6, 2026, 5:10 a.m.
Created at: March 4, 2026, 7:30 p.m.