Triple
T9589824
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Demchugdongrub |
E231387
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | collaborator with Imperial Japan |
C26789
|
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: collaborator with Imperial Japan Context triple: [Demchugdongrub, instanceOf, collaborator with Imperial Japan]
-
A.
collaborator with Nazi Germany
A collaborator with Nazi Germany is an individual, group, or government that actively cooperated with or supported the policies, military efforts, or occupation authorities of the Third Reich during its period of power, often to gain advantage or out of ideological alignment.
-
B.
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.
-
C.
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.
-
D.
Japanese warlord
A Japanese warlord is a powerful feudal military leader who commands samurai and territories, often vying for political dominance during periods of civil strife such as the Sengoku era.
-
E.
Japanese colonial administrator
A Japanese colonial administrator is an official appointed by the Japanese government to govern, manage, and implement imperial policies in occupied or colonized territories.
- 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_69ca8482884481908eccdfdf64d6fbf7 |
completed | March 30, 2026, 2:11 p.m. |
Created at: March 30, 2026, 8:06 p.m.