Triple
T17688400
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sadaijin |
E440957
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | imperial Japanese office |
C2921
|
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 office Context triple: [Sadaijin, instanceOf, imperial Japanese office]
-
A.
Japanese imperial office
chosen
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 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.
-
C.
Cabinet of Japan
The Cabinet of Japan is the executive branch of the Japanese government, consisting of the Prime Minister and other ministers who collectively direct and control national administration.
-
D.
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.
-
E.
government agency of Japan
A government agency of Japan is an official administrative body established by the Japanese government to implement laws, deliver public services, and manage specific policy areas at the national level.
- 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_69d8b9e940b081908b862bb0e6e89b0d |
completed | April 10, 2026, 8:50 a.m. |
Created at: April 10, 2026, 10:03 a.m.