Triple
T33448709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | charters of the Teutonic Order |
E856575
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval legal document collection |
C41907
|
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 legal document collection Context triple: [charters of the Teutonic Order, instanceOf, medieval legal document collection]
-
A.
medieval law book
chosen
A medieval law book is a manuscript or early printed volume compiling legal codes, statutes, and case decisions used to record, interpret, and apply the laws of a medieval society.
-
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.
collection of ecclesiastical documents
A collection of ecclesiastical documents is an organized set of official church writings—such as decrees, letters, liturgical texts, and doctrinal statements—preserved for reference, governance, and historical record within a religious community.
-
D.
medieval law
Medieval law is the body of legal customs, codes, and practices that governed social, economic, and political life in Europe during the Middle Ages, blending local traditions, feudal obligations, royal decrees, and canon (church) law.
-
E.
historical legal text
A historical legal text is a written document from a past era that records laws, legal decisions, or legal reasoning, reflecting the legal norms, institutions, and societal values of its time.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
Created at: May 1, 2026, 1:37 a.m.