Triple
T27130093
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Austrian Empire surname laws |
E681539
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical legal regime |
C34597
|
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 regime Context triple: [Austrian Empire surname laws, instanceOf, historical legal regime]
-
A.
historical legal tradition
A historical legal tradition is a long-established system of laws, principles, and practices that has developed over time within a particular society or culture, shaping its legal institutions and norms.
-
B.
historical legal category
A historical legal category is a classification used in past legal systems to group people, actions, or entities under specific rights, obligations, or statuses that reflected the social, political, and economic structures of its time.
-
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.
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.
-
E.
historical system
chosen
A historical system is an organized framework of interrelated events, structures, and processes that evolve over time and shape the development and understanding of past societies.
- 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_69eefacbcc2081909ebf00daa23f1981 |
completed | April 27, 2026, 5:57 a.m. |
Created at: April 27, 2026, 9:03 a.m.