Triple

T35372648
Position Surface form Disambiguated ID Type / Status
Subject Battle of Sirmium (1167) E1021816 entity
Predicate overlordRulerByzantineSide P108801 FINISHED
Object Emperor Manuel I Komnenos 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: Emperor Manuel I Komnenos | Statement: [Battle of Sirmium (1167), overlordRulerByzantineSide, Emperor Manuel I Komnenos]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: overlordRulerByzantineSide
Context triple: [Battle of Sirmium (1167), overlordRulerByzantineSide, Emperor Manuel I Komnenos]
  • A. ByzantineEmperorInCommand
    Indicates that a person holds and exercises the supreme ruling and military authority as the Byzantine emperor.
  • B. ByzantineEmperorDuringConflict chosen
    Indicates that a person held the office of Byzantine Emperor during the time span of a specified conflict.
  • C. allyOfByzantines
    Indicates a relationship where an entity served as an ally or cooperative partner of the Byzantine Empire.
  • D. ByzantineCommander
    Indicates a relationship where an entity holds the role or function of a commander within a Byzantine military or organizational context.
  • E. opponentOfByzantines
    Indicates a relationship where an entity is an adversary or enemy of the Byzantines in a conflict or rivalry.
  • 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_69f76df000488190ab7c97f565677055 completed May 3, 2026, 3:46 p.m.
NER Named-entity recognition batch_69f79da9f80c8190b0afd8509f28747b completed May 3, 2026, 7:10 p.m.
PD Predicate disambiguation batch_69f79617d40481909ba372f94209c08b completed May 3, 2026, 6:38 p.m.
Created at: May 3, 2026, 4:03 p.m.