Triple

T6371388
Position Surface form Disambiguated ID Type / Status
Subject Killing of John Comyn at Greyfriars Church, Dumfries E143352 entity
Predicate instanceOf P0 FINISHED
Object medieval conflict incident C12823 CONCEPT FINISHED

How this triple was built (1 step)

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.

CD Concept disambiguation gpt-5-mini-2025-08-07
Target class: medieval conflict incident
Context triple: [Killing of John Comyn at Greyfriars Church, Dumfries, instanceOf, medieval conflict incident]
  • A. medieval event
    A medieval event is a historically themed gathering or occurrence set in or inspired by the Middle Ages, often featuring period-appropriate customs, attire, activities, and social structures.
  • B. 13th-century conflict chosen
    A 13th-century conflict is a military or political struggle that occurred between 1201 and 1300, shaped by medieval feudal structures, religious motivations, and emerging state powers.
  • C. war in the Middle Ages
    War in the Middle Ages encompasses the organized, often feudal-based conflicts fought between kingdoms, nobles, and religious powers using evolving military technologies, tactics, and social structures from roughly the 5th to the 15th century.
  • D. conflict in the Holy Roman Empire
    Conflict in the Holy Roman Empire encompasses the political, religious, and territorial struggles among emperors, princes, cities, and external powers that shaped the empire’s fragmented structure and shifting balance of authority.
  • E. 16th-century conflict
    A 16th-century conflict is a historically documented military, political, or religious struggle that occurred between 1501 and 1600, involving organized groups or states and significantly influencing the social and geopolitical landscape of the early modern period.
  • F. None of above.

Provenance (1 batch)

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_69c008d8c61081908bcaf61510d881ed completed March 22, 2026, 3:20 p.m.
Created at: March 22, 2026, 4:33 p.m.