Triple
T21748011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 関東軍司令官 |
E536836
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | 旧日本陸軍の高級将官ポスト |
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: 旧日本陸軍の高級将官ポスト Context triple: [関東軍司令官, instanceOf, 旧日本陸軍の高級将官ポスト]
-
A.
Imperial Japanese military rank
Imperial Japanese military rank is a hierarchical designation used in the armed forces of the Empire of Japan to define authority, responsibility, and status among its military personnel.
-
B.
position in the Japan Self-Defense Forces
A position in the Japan Self-Defense Forces represents a specific role or post within its organizational structure, defined by rank, duties, and assigned responsibilities in defense and support operations.
-
C.
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.
-
D.
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.
-
E.
military office
A military office is an administrative workspace within an armed forces organization where personnel manage planning, logistics, communication, and documentation to support 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_69e0c46eab808190b848242d63a17c47 |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:50 p.m.