Triple

T22773158
Position Surface form Disambiguated ID Type / Status
Subject Emperor Carus E563612 entity
Predicate spouse P13 FINISHED
Object Magnia Urbica NE NERFINISHED

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: Magnia Urbica | Statement: [Emperor Carus, spouse, Magnia Urbica]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Magnia Urbica
Context triple: [Emperor Carus, spouse, Magnia Urbica]
  • A. Magnia Urbica chosen
    Magnia Urbica was a Roman empress of the late 3rd century, known primarily as the wife of Emperor Carus and mother of the emperors Carinus and Numerian.
  • B. Caia
    Caia is a town and district in central Mozambique, situated along the Zambezi River in Sofala Province.
  • C. Maenza
    Maenza is a small historic town in the Lazio region of central Italy, known for its medieval architecture and hilltop setting.
  • D. Statilia
    Statilia is an ancient Roman feminine praenomen (given name) most notably borne by the empress Statilia Messalina, wife of Emperor Nero.
  • E. Oropus
    Oropus was an ancient Greek town on the border of Attica and Boeotia, best known for its sanctuary and oracle of the hero Amphiaraus.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (2 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_69e24554497c819080b996e071de27c2 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17b6040048190a36fa759e06136ea completed April 29, 2026, 3:30 a.m.
Created at: April 17, 2026, 3:27 p.m.