Triple
T22482439
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial House Law of 1947 |
E555799
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial household law |
C19522
|
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: imperial household law Context triple: [Imperial House Law of 1947, instanceOf, imperial household law]
-
A.
dynastic legal code
A dynastic legal code is a formalized set of laws and regulations established and enforced by a ruling dynasty to govern its subjects, institutions, and social order.
-
B.
Thai royal law
Thai royal law is the body of legal principles, customs, and statutes that define the powers, duties, privileges, and succession of the Thai monarchy and regulate its relationship with the state and citizens.
-
C.
Roman imperial household
The Roman imperial household comprised the emperor’s family, slaves, freedmen, and administrative staff who managed both the private affairs and many public functions of the imperial court.
-
D.
imperial estate
An imperial estate is a large, centrally administered landholding owned or controlled by an emperor or imperial authority, typically encompassing agricultural, residential, and administrative functions that support the imperial household and governance.
-
E.
Japanese imperial law
chosen
Japanese imperial law is the body of legal principles, statutes, and institutional practices that governed the authority, succession, and functions of the Emperor and imperial household within Japan’s historical and constitutional frameworks.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:49 p.m.