Triple

T20971872
Position Surface form Disambiguated ID Type / Status
Subject Battle of Dyrrhachium (1107–1108 campaign) E516518 entity
Predicate aimOfByzantines P142309 FINISHED
Object defense of Dyrrhachium stronghold 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: defense of Dyrrhachium stronghold | Statement: [Battle of Dyrrhachium (1107–1108 campaign), aimOfByzantines, defense of Dyrrhachium stronghold]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: aimOfByzantines
Context triple: [Battle of Dyrrhachium (1107–1108 campaign), aimOfByzantines, defense of Dyrrhachium stronghold]
  • A. allyOfByzantines
    Indicates a relationship where an entity served as an ally or cooperative partner of the Byzantine Empire.
  • B. strategyUsedByByzantines
    Indicates a strategic method or tactic that was employed by the Byzantines.
  • C. aimOfRome
    Indicates that something is the goal, purpose, or intended objective of Rome.
  • D. primaryByzantineForces
    Indicates that the referenced forces constitute the main or principal military contingent of the Byzantine side in a given context or engagement.
  • E. statusInByzantineEmpire
    Indicates the role, rank, or condition an entity held within the political or social structure of the Byzantine Empire.
  • F. None of above. chosen

Provenance (4 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_69e0b4fee5ac8190875fa9ceba1a5e5e completed April 16, 2026, 10:07 a.m.
NER Named-entity recognition batch_69e6fba161d88190b8905891f449004e completed April 21, 2026, 4:22 a.m.
PD Predicate disambiguation batch_69e5dbe6976081908abd4e9c8734bae9 completed April 20, 2026, 7:55 a.m.
PDg Predicate description generation batch_69e5e2df1a888190b5b478e76bdf7fdf completed April 20, 2026, 8:25 a.m.
Created at: April 16, 2026, 1:44 p.m.