Triple

T35372658
Position Surface form Disambiguated ID Type / Status
Subject Battle of Sirmium (1167) E1021816 entity
Predicate militaryBranchByzantine P73300 FINISHED
Object Byzantine field army 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: Byzantine field army | Statement: [Battle of Sirmium (1167), militaryBranchByzantine, Byzantine field army]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militaryBranchByzantine
Context triple: [Battle of Sirmium (1167), militaryBranchByzantine, Byzantine field army]
  • A. allyOfByzantines
    Indicates a relationship where an entity served as an ally or cooperative partner of the Byzantine Empire.
  • B. primaryByzantineForces chosen
    Indicates that the referenced forces constitute the main or principal military contingent of the Byzantine side in a given context or engagement.
  • C. ByzantineCommander
    Indicates a relationship where an entity holds the role or function of a commander within a Byzantine military or organizational context.
  • D. RomanArmyType
    Indicates the specific organizational or functional category to which a Roman military force belongs (e.g., legion, auxiliary, navy).
  • E. ByzantineEmperorInCommand
    Indicates that a person holds and exercises the supreme ruling and military authority as the Byzantine emperor.
  • 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_69fd02680d948190a3463fb119ba8556 completed May 7, 2026, 9:21 p.m.
PD Predicate disambiguation batch_69fcf89c69b4819082bbc564bd15137d completed May 7, 2026, 8:39 p.m.
Created at: May 3, 2026, 4:03 p.m.