Triple
T26916099
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Annotationes in XXIV libros Pandectarum |
E677520
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Renaissance legal text |
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: Renaissance legal text Context triple: [Annotationes in XXIV libros Pandectarum, instanceOf, Renaissance legal text]
-
A.
Renaissance treatise
A Renaissance treatise is a systematic, often humanist-influenced written work from roughly the 14th to 17th centuries that explores a specific subject—such as art, science, politics, or philosophy—through structured argument and scholarly discourse.
-
B.
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.
-
C.
Renaissance literature work
A Renaissance literature work is a written piece, typically from the 14th to 17th centuries, that reflects the era’s revival of classical learning, humanist ideals, and experimentation with new literary forms and vernacular languages.
-
D.
medieval law book
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.
-
E.
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.
- 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_69eee9bdebc48190ba90a12a63e09c73 |
completed | April 27, 2026, 4:44 a.m. |
Created at: April 27, 2026, 6:04 a.m.