Triple

T14410547
Position Surface form Disambiguated ID Type / Status
Subject Gundobad E357310 entity
Predicate roleInRomanPolitics P39445 FINISHED
Object kingmaker in late Western Roman Empire 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: kingmaker in late Western Roman Empire | Statement: [Gundobad, roleInRomanPolitics, kingmaker in late Western Roman Empire]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: roleInRomanPolitics
Context triple: [Gundobad, roleInRomanPolitics, kingmaker in late Western Roman Empire]
  • A. roleInRome chosen
    Indicates that an entity holds or held a specific role, position, or function within the context of Rome or Roman society.
  • B. RomanRepresentative
    Indicates that one entity serves as an official representative or agent of the Roman state, authority, or interests in relation to another entity.
  • C. RomanCommander
    Indicates a relationship where an entity holds the role or position of a commander within a Roman military or organizational context.
  • D. governedAsCaesar
    Indicates that an entity exercised ruling authority in the capacity or role of a Caesar (emperor).
  • E. romanNomen
    Indicates that an entity has a specific Roman nomen, i.e., the clan or gens name within the traditional Roman naming system.
  • 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_69d82793421c8190861eb0e673b085de completed April 9, 2026, 10:26 p.m.
NER Named-entity recognition batch_69de90c9b3448190aec1608836a5e913 completed April 14, 2026, 7:08 p.m.
PD Predicate disambiguation batch_69de2aa1b57881909a033eac8545c417 completed April 14, 2026, 11:53 a.m.
Created at: April 10, 2026, 1:17 a.m.