Triple

T10885228
Position Surface form Disambiguated ID Type / Status
Subject Magnentius E257024 entity
Predicate appointedDecentiusCaesar P96233 FINISHED
Object 351 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: 351 | Statement: [Magnentius, appointedDecentiusCaesar, 351]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: appointedDecentiusCaesar
Context triple: [Magnentius, appointedDecentiusCaesar, 351]
  • A. successorAsGallicEmperor
    Indicates that one entity became the next Gallic Emperor following another in the line of succession.
  • B. successorAsCaesarOfTheEast
    Indicates that one individual became the next holder of the title or role of Caesar of the Eastern Roman Empire after another individual.
  • C. successorAsEasternAugustus
    Indicates that one entity becomes the next holder of the title of Eastern Augustus immediately following another entity in succession.
  • D. predecessorAsCaesarOfTheEast
    Indicates that one entity previously held the position of Caesar of the East immediately before the other entity in an official succession.
  • E. ByzantineEmperorInCommand
    Indicates that a person holds and exercises the supreme ruling and military authority as the Byzantine emperor.
  • 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_69d6aa848804819081b2713ca0bedf06 completed April 8, 2026, 7:20 p.m.
NER Named-entity recognition batch_69d751dd6a3c81909965ef774e8b7309 completed April 9, 2026, 7:14 a.m.
PD Predicate disambiguation batch_69d70d3943c881908895397eccc3e415 completed April 9, 2026, 2:21 a.m.
PDg Predicate description generation batch_69d7101de31c819090707635f6790559 completed April 9, 2026, 2:34 a.m.
Created at: April 8, 2026, 9:21 p.m.