Triple
T13713366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lords Appellant crisis |
E328830
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | late medieval English political event |
C15945
|
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 English political event Context triple: [Lords Appellant crisis, instanceOf, late medieval English political 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.
event in British history
chosen
A significant occurrence or series of actions within the geographical and political context of Britain that influenced its social, political, economic, or cultural development and is recognized as part of its historical narrative.
-
C.
medieval parliament
A medieval parliament is an assembly of nobles, clergy, and sometimes commoners convened by a monarch to advise on governance, consent to taxation, and address matters of law and policy.
-
D.
medieval political agreement
A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
-
E.
13th-century event
A 13th-century event is any significant occurrence, development, or happening that took place between the years 1201 and 1300 CE.
- 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_69d80770b9bc81909f70c8c317d53cff |
completed | April 9, 2026, 8:09 p.m. |
Created at: April 9, 2026, 9:54 p.m.