Triple

T20320906
Position Surface form Disambiguated ID Type / Status
Subject Disputation of Paris E492203 entity
Predicate instanceOf P0 FINISHED
Object event in medieval France C32777 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: event in medieval France
Context triple: [Disputation of Paris, instanceOf, event in medieval France]
  • 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. Frankish history event
    A Frankish history event is a significant occurrence involving the Frankish peoples, kingdoms, or rulers that shaped the political, social, or cultural development of early medieval Western Europe.
  • C. event in the Burgundian Wars
    An event in the Burgundian Wars is a specific historical occurrence—such as a battle, treaty, siege, or political maneuver—that took place during the series of conflicts between the Duchy of Burgundy and its various European adversaries in the late 15th century.
  • D. event in the Albigensian Crusade chosen
    An "event in the Albigensian Crusade" is a specific historical occurrence—such as a battle, siege, council, treaty, or massacre—that took place within the context and timeframe of the early 13th-century papal military campaign against the Cathars in southern France.
  • E. event of the French Wars of Religion
    An event of the French Wars of Religion is a historically specific occurrence—such as a battle, edict, massacre, negotiation, or political maneuver—directly related to the religious and civil conflicts between Catholics and Protestants in France between 1562 and 1598.
  • 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_69e0b4a0134081909113563e1c3ba68a completed April 16, 2026, 10:06 a.m.
Created at: April 16, 2026, 11:20 a.m.