Triple
T5905373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imperial succession |
E131329
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese imperial institution |
C6483
|
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: Japanese imperial institution Context triple: [Imperial succession, instanceOf, Japanese imperial institution]
-
A.
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.
-
B.
Edo period institution
An Edo period institution is an organized social, political, economic, or cultural structure that operated in Japan between 1603 and 1868 under Tokugawa rule, shaping and regulating aspects of daily life and governance.
-
C.
imperial institution
chosen
An imperial institution is a formal organization or structure established by an empire to administer, control, and legitimize its authority over territories and populations.
-
D.
peer of the Empire of Japan
A peer of the Empire of Japan was a member of the kazoku hereditary nobility, holding aristocratic rank and privileges under the Meiji Constitution and subsequent imperial government.
-
E.
Japanese government doctrine
Japanese government doctrine refers to the evolving set of principles, legal interpretations, and policy norms that guide Japan’s constitutional governance, security policy, and administrative decision-making within the framework of its pacifist constitution and parliamentary democracy.
- 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_69c0085864a88190a569c05ff7d65f29 |
completed | March 22, 2026, 3:18 p.m. |
Created at: March 22, 2026, 3:59 p.m.