Triple
T2287573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Statutes of Westminster |
E51428
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval legislation |
C9503
|
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 legislation Context triple: [Statutes of Westminster, instanceOf, medieval legislation]
-
A.
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.
-
B.
medieval nobility
Medieval nobility comprised the hereditary warrior-elite who held land from a monarch in exchange for military and political service, dominating social, economic, and legal life in feudal Europe.
-
C.
ancient Near Eastern law collection
An ancient Near Eastern law collection is a compiled set of legal rules, case decisions, and royal decrees from early civilizations such as Mesopotamia, intended to articulate social norms, regulate behavior, and legitimize authority.
-
D.
medieval people
Medieval people are individuals living during the Middle Ages, typically characterized by feudal social structures, agrarian lifestyles, religious centrality, and limited technological development compared to later periods.
-
E.
Byzantine law code
A Byzantine law code is a systematically organized collection of legal rules, imperial edicts, and judicial interpretations that governed civil, criminal, and ecclesiastical matters in the Byzantine Empire.
- F. None of above. chosen
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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:48 p.m.