Triple

T2001791
Position Surface form Disambiguated ID Type / Status
Subject Petronius Maximus E43486 entity
Predicate praetorianPrefectOfGaulEnd P35046 FINISHED
Object c. 443 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: c. 443 | Statement: [Petronius Maximus, praetorianPrefectOfGaulEnd, c. 443]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: praetorianPrefectOfGaulEnd
Context triple: [Petronius Maximus, praetorianPrefectOfGaulEnd, c. 443]
  • A. predecessorAsEasternAugustus
    Indicates that one entity previously held the position of Eastern Roman Emperor immediately before the other entity.
  • B. reignAsAugustusOfTheWest
    Indicates that a person holds or exercises the imperial authority and title of Augustus over the Western Roman Empire.
  • C. successorAsEasternAugustus
    Indicates that one entity becomes the next holder of the title of Eastern Augustus immediately following another entity in succession.
  • D. RomanRepresentative
    Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
  • E. romanRuleEnded
    Indicates that a period of Roman political or administrative control over a place or people has come to an end.
  • 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_69a88715dbbc8190b2299e29e955d997 completed March 4, 2026, 7:25 p.m.
NER Named-entity recognition batch_69abb880c710819098fb877052ce56dc completed March 7, 2026, 5:32 a.m.
PD Predicate disambiguation batch_69abb79e63c08190982c8b44a557266f completed March 7, 2026, 5:29 a.m.
PDg Predicate description generation batch_69abb87b9fc08190a748c278ef2d7dc7 completed March 7, 2026, 5:32 a.m.
Created at: March 4, 2026, 7:37 p.m.