Triple

T17819572
Position Surface form Disambiguated ID Type / Status
Subject Philippicus Bardanes E444939 entity
Predicate militarySetback P117819 FINISHED
Object Bulgar victory near Constantinople 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: Bulgar victory near Constantinople | Statement: [Philippicus Bardanes, militarySetback, Bulgar victory near Constantinople]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: militarySetback
Context triple: [Philippicus Bardanes, militarySetback, Bulgar victory near Constantinople]
  • A. sufferedSetback chosen
    Indicates that an entity has experienced a negative event or obstacle that hindered its progress or success.
  • B. militaryConsequence
    Indicates a causal relationship where one event, action, or condition leads to a specific outcome or effect in the military domain (such as changes in capability, strategy, or conflict status).
  • C. significantDefeat
    Indicates that one entity has decisively and substantially defeated another, implying a clear and impactful victory rather than a narrow or marginal one.
  • D. militaryMeasure
    Indicates a relationship where an entity undertakes, imposes, or is subject to a specific military-related action, policy, or operational measure.
  • E. wasMilitarized
    Indicates that an entity underwent a process of being organized, equipped, or adapted for military use or purposes.
  • 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_69d8b9f0de78819099395b14db75a8a6 completed April 10, 2026, 8:50 a.m.
NER Named-entity recognition batch_69e489101aa48190a1439d8cb683bba9 completed April 19, 2026, 7:49 a.m.
PD Predicate disambiguation batch_69e3d8de28688190844b65acf6af54e6 completed April 18, 2026, 7:17 p.m.
Created at: April 10, 2026, 10:15 a.m.