Triple
T29478333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | French annexation of the Duchy of Burgundy |
E747711
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late medieval event |
C18980
|
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: late medieval event Context triple: [French annexation of the Duchy of Burgundy, instanceOf, late medieval event]
-
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 event
A 13th-century event is any significant occurrence, development, or happening that took place between the years 1201 and 1300 CE.
-
C.
medieval era
The medieval era is a historical period roughly spanning the 5th to the 15th century in Europe, characterized by feudal societies, the dominance of the Catholic Church, and the gradual emergence of towns, universities, and nation-states.
-
D.
14th-century event
chosen
A 14th-century event is a historically significant occurrence between 1301 and 1400 that influenced the social, political, cultural, or economic developments of that period.
-
E.
medieval historical phenomenon
A medieval historical phenomenon is a significant social, political, economic, cultural, or religious development that emerged or transformed societies during the Middle Ages, typically between the 5th and 15th centuries.
- 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_69f0bd43ba30819095eb1cfc3adf525c |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 28, 2026, 4:02 p.m.