Triple
T8292810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stannary Convocation |
E193940
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval legislative body |
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 legislative body Context triple: [Stannary Convocation, instanceOf, medieval legislative body]
-
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 legislation
Medieval legislation encompasses the body of laws, decrees, and legal customs established by monarchs, feudal lords, and religious authorities in Europe during the Middle Ages to regulate social order, property, crime, and governance.
-
C.
legislative body
A legislative body is an organized group of elected or appointed representatives empowered to create, amend, and repeal laws and oversee government policy within a political system.
-
D.
provisional legislative body
A provisional legislative body is a temporary lawmaking assembly established to exercise legislative authority during a transitional or interim period before a permanent government structure is formed or restored.
-
E.
group of medieval polities
A group of medieval polities is a collection of semi-autonomous kingdoms, principalities, city-states, or other territorial entities that interacted through shifting alliances, conflicts, and hierarchies within the broader sociopolitical landscape of the Middle Ages.
- 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_69ca82e32db481908b72f3804fa71152 |
completed | March 30, 2026, 2:04 p.m. |
Created at: March 30, 2026, 5:52 p.m.