Triple

T2100875
Position Surface form Disambiguated ID Type / Status
Subject Emperor of the Romans E37088 entity
Predicate claimsSuccessionFrom P7973 FINISHED
Object ancient Roman emperors 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: ancient Roman emperors | Statement: [Emperor of the Romans, claimsSuccessionFrom, ancient Roman emperors]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: claimsSuccessionFrom
Context triple: [Emperor of the Romans, claimsSuccessionFrom, ancient Roman emperors]
  • A. 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.
  • B. successionOrder
    Indicates the ordered sequence in which entities are designated to succeed or take over a role, position, or title.
  • C. hasSuccession
    Indicates that one entity follows or replaces another in a sequence, order, or position, forming a succession relationship between them.
  • D. successionTrigger
    Indicates a condition or event that initiates or causes a transfer of position, role, or authority from one entity to another.
  • E. dynasticClaim chosen
    Indicates a relationship where one party asserts a hereditary or lineage-based right to rule, inherit, or hold authority over another.
  • 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_69a8861828948190924aa30c08806b3a completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69abbabb512c819087b1d5ec8ef11e63 completed March 7, 2026, 5:42 a.m.
PD Predicate disambiguation batch_69abb7b6274081909df36cd7a7c6a675 completed March 7, 2026, 5:29 a.m.
Created at: March 4, 2026, 7:43 p.m.