Triple
T3019500
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | College of Princes |
E82419
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | council of the Imperial Diet |
C5136
|
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: council of the Imperial Diet Context triple: [College of Princes, instanceOf, council of the Imperial Diet]
-
A.
Act of the Diet of Japan
An Act of the Diet of Japan is a formal law enacted by Japan’s national legislature, consisting of the House of Representatives and the House of Councillors, through its prescribed legislative process.
-
B.
Japanese imperial office
A Japanese imperial office is a governmental or court position within the historical or modern Japanese imperial system, responsible for specific administrative, ceremonial, or advisory functions under the authority of the Emperor.
-
C.
Zemsky Sobor
Zemsky Sobor was a representative assembly in 16th–17th century Russia, convened by the tsar to consult nobles, clergy, and other estates on major state matters such as succession, legislation, and foreign policy.
-
D.
imperial diet
chosen
An imperial diet is a formal deliberative assembly of representatives from various territories within an empire, convened by the sovereign to legislate, advise, and address matters of state.
-
E.
imperial court office
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
- 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_69ad8b1fb34081908c1b873e2b7273e1 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3 p.m.