Triple
T24258352
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Authenticum |
E604634
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | medieval Latin legal 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 Latin legal collection Context triple: [Authenticum, instanceOf, medieval Latin legal 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.
late Roman legal codex
A late Roman legal codex is a formally compiled, systematically organized collection of imperial laws, juristic writings, and legal principles produced in the later Roman Empire to standardize and preserve authoritative legal practice.
-
C.
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.
-
D.
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.
-
E.
medieval jurist
A medieval jurist is a legal scholar or practitioner in the Middle Ages who interprets, systematizes, and applies contemporary laws—often Roman, canon, or customary law—within courts, universities, or ecclesiastical institutions.
- 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_69e29544c29c8190b023606eafe5d36a |
completed | April 17, 2026, 8:17 p.m. |
Created at: April 18, 2026, 12:06 a.m.