Triple
T18543533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acts of Settlement and Explanation |
E453163
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 17th-century legislation |
C18321
|
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: 17th-century legislation Context triple: [Acts of Settlement and Explanation, instanceOf, 17th-century legislation]
-
A.
19th-century legislation
19th-century legislation encompasses the body of laws and legal reforms enacted during the 1800s that shaped modern nation-states, industrial societies, and evolving civil rights frameworks.
-
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.
early modern legal codification
chosen
Early modern legal codification is the systematic collection, organization, and formal enactment of laws in comprehensive written codes by emerging centralized states between roughly the 16th and 18th centuries.
-
D.
17th-century town
A 17th-century town is a small, historically situated settlement characterized by pre-industrial architecture, localized trade and governance, and social life organized around markets, churches, and craft guilds.
-
E.
17th-century book
A 17th-century book is a bound collection of printed or handwritten pages produced between 1601 and 1700, reflecting the period’s materials, typography, and intellectual, religious, or political culture.
- 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_69d8d388b0c881908e610a1c45b52640 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:38 a.m.