Triple
T34254186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reorganized National Government of the Republic of China |
E878824
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | client state of the Empire of Japan |
C60567
|
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: client state of the Empire of Japan Context triple: [Reorganized National Government of the Republic of China, instanceOf, client state of the Empire of Japan]
-
A.
Japanese state
The Japanese state is the centralized political and legal authority governing Japan, encompassing its institutions, laws, territory, and international sovereignty.
-
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.
Tai state
A Tai state is a traditional political entity or kingdom historically established and governed by Tai-speaking peoples in regions of Southeast and parts of South and East Asia.
-
E.
client state of the Roman Empire
A client state of the Roman Empire was a formally independent polity that maintained its own rulers and internal administration while being bound by treaty to support Roman foreign policy, pay tribute or provide troops, and accept Roman influence over its succession and external affairs.
- 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_69f349b421cc8190b4b4655e1d612548 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 1:56 a.m.