Triple

T30540065
Position Surface form Disambiguated ID Type / Status
Subject Pescennius Niger E777248 entity
Predicate rivalClaimantTo P148278 FINISHED
Object Didius Julianus 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: Didius Julianus | Statement: [Pescennius Niger, rivalClaimantTo, Didius Julianus]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: rivalClaimantTo
Context triple: [Pescennius Niger, rivalClaimantTo, Didius Julianus]
  • A. rivalClaimant chosen
    Indicates a relationship where two or more parties each assert competing rights or titles to the same position, asset, or claim, placing them in direct opposition.
  • B. successorClaimant
    Indicates that one entity is the next or replacement claimant to a right, title, or claim previously held by another entity.
  • C. removedRivalClaimant
    Indicates that one entity eliminated or displaced another entity who was competing with them for a particular position, title, or claim.
  • D. reignClaim
    Indicates a claim or assertion by an entity that it has the right to rule or hold sovereign authority over a domain or people.
  • E. successorDynasticClaimant
    Indicates that one entity is the next recognized claimant to a dynastic title, throne, or inheritance following another entity.
  • 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_69f2249d183c8190b79937c1768d2163 completed April 29, 2026, 3:32 p.m.
NER Named-entity recognition batch_69f6888953688190ae6709934cc9fccd completed May 2, 2026, 11:28 p.m.
PD Predicate disambiguation batch_69f67e42d6688190b60e91d2c388c555 completed May 2, 2026, 10:44 p.m.
Created at: April 29, 2026, 8:19 p.m.