Triple
T10305015
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Corpus Iuris Canonici |
E241729
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical legal compilation |
C21846
|
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: historical legal compilation Context triple: [Corpus Iuris Canonici, instanceOf, historical legal compilation]
-
A.
historical legal text
chosen
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.
-
B.
statutory compilation
A statutory compilation is an organized collection of statutes, often arranged by subject or jurisdiction, that consolidates and presents the text of enacted laws in a systematic, accessible format.
-
C.
early modern legal codification
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.
compilation of oral law
A compilation of oral law is an organized written collection of previously unwritten legal traditions, interpretations, and rulings that were transmitted orally within a community or religious-legal system.
-
E.
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.
- 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_69d381ac38808190a8ca7457c85b625b |
completed | April 6, 2026, 9:49 a.m. |
Created at: April 6, 2026, 11:46 a.m.