Triple
T11256085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gensui |
E266441
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Imperial Japanese military rank |
C29447
|
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 military rank Context triple: [Gensui, instanceOf, Imperial Japanese military rank]
-
A.
North Korean military rank
A North Korean military rank is a formal title within the Korean People's Army hierarchy that signifies an individual's level of authority, responsibility, and status in the armed forces of the Democratic People's Republic of Korea.
-
B.
Soviet military rank position
A Soviet military rank position represents a specific hierarchical status and role within the armed forces of the former Soviet Union, defining an individual's authority, responsibilities, and command relationships.
-
C.
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.
-
D.
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.
-
E.
Nazi Germany military rank
A Nazi Germany military rank represents a specific hierarchical position within the armed forces of the Third Reich, defining an individual's authority, responsibilities, and status in the military structure.
- F. None of above. chosen
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_69d6aac7953c8190b82caf9d7640fdf9 |
completed | April 8, 2026, 7:21 p.m. |
Created at: April 8, 2026, 9:31 p.m.