Triple

T29672027
Position Surface form Disambiguated ID Type / Status
Subject Byzantine–Armenian wars E750699 entity
Predicate primaryObjectiveOfByzantium P142309 FINISHED
Object direct imperial control over Armenian territories 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: direct imperial control over Armenian territories | Statement: [Byzantine–Armenian wars, primaryObjectiveOfByzantium, direct imperial control over Armenian territories]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: primaryObjectiveOfByzantium
Context triple: [Byzantine–Armenian wars, primaryObjectiveOfByzantium, direct imperial control over Armenian territories]
  • A. aimOfByzantines chosen
    Indicates the goal or objective pursued by the Byzantines in a given context.
  • B. primaryObjectiveOfEmpire
    Indicates the main strategic goal or overarching purpose that an empire seeks to achieve or maintain.
  • C. impactOnByzantines
    Indicates the effect or influence that something has on the Byzantines.
  • D. allyOfByzantines
    Indicates a relationship where an entity served as an ally or cooperative partner of the Byzantine Empire.
  • E. primaryByzantineForces
    Indicates that the referenced forces constitute the main or principal military contingent of the Byzantine side in a given context or engagement.
  • 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_69f0d62418a08190a401b127adf9f8a6 completed April 28, 2026, 3:45 p.m.
NER Named-entity recognition batch_6a016777257081908841c5522dfa76e6 completed May 11, 2026, 5:21 a.m.
PD Predicate disambiguation batch_6a0164e49bec8190af3c8626be9677a9 completed May 11, 2026, 5:11 a.m.
Created at: April 28, 2026, 7:05 p.m.