Triple
T23361951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Habsburg law |
E593206
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical legal tradition |
C47576
|
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 tradition Context triple: [Habsburg law, instanceOf, historical legal tradition]
-
A.
historical legal concept
A historical legal concept is an idea, principle, or doctrine from past legal systems that shaped how laws were interpreted, applied, and evolved over time.
-
B.
civil law tradition
The civil law tradition is a legal system rooted in comprehensive written codes and statutes, derived primarily from Roman law, in which judges apply and interpret codified rules rather than relying heavily on judicial precedent.
-
C.
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.
-
D.
Italic legal tradition
Italic legal tradition refers to the body of customary laws, legal practices, and institutions that developed among the ancient Italic peoples (including Romans and neighboring communities) prior to and alongside the formalization of Roman law, shaping early concepts of rights, obligations, and civic order in the Italian peninsula.
-
E.
legal history
Legal history is the study of how laws, legal institutions, and legal ideas have developed and changed over time within their broader social, political, and cultural contexts.
- F. None of above. chosen
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_69e25d24d2a4819092e6ede74c2a918d |
completed | April 17, 2026, 4:17 p.m. |
Created at: April 17, 2026, 5:30 p.m.