Triple
T24488555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Daijō-daikan |
E617580
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial Japanese 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: imperial Japanese institution Context triple: [Daijō-daikan, instanceOf, imperial Japanese 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.
Imperial Japanese Army institution
An Imperial Japanese Army institution is an organizational entity—such as a school, bureau, or research center—established to train personnel, develop doctrine, manage logistics, or support the operational and administrative functions of the Imperial Japanese Army.
-
C.
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.
-
D.
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.
-
E.
Japanese military administration unit
A Japanese military administration unit is an organizational entity within Japan’s armed forces responsible for managing logistics, personnel, planning, and support functions necessary to sustain military operations.
- 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_69e2d7f4e6bc8190aec540ae3b9ed7f2 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 2:22 a.m.