Triple
T31764008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cortes of León |
E810757
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval representative assembly |
C11597
|
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 representative assembly Context triple: [Cortes of León, instanceOf, medieval representative assembly]
-
A.
medieval parliament
chosen
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.
-
B.
medieval Slavic popular assembly
A medieval Slavic popular assembly was a communal gathering of free inhabitants who collectively deliberated and decided on political, legal, and military matters within their community or principality.
-
C.
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.
-
D.
nobility assembly house
A nobility assembly house is a formal building where members of the aristocracy gather for political deliberation, social events, and the administration of noble affairs.
-
E.
medieval polity
A medieval polity is a territorially based political entity of the Middle Ages—such as a kingdom, duchy, city-state, or principality—defined by overlapping authorities, personal allegiances, and often fragmented sovereignty rather than a centralized nation-state structure.
- 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_69f348e463e08190b902d4819195e1f0 |
completed | April 30, 2026, 12:19 p.m. |
Created at: April 30, 2026, 11:31 p.m.