Triple
T4952904
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Puyi |
E111210
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Manchukuo emperor |
C16675
|
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: Manchukuo emperor Context triple: [Puyi, instanceOf, Manchukuo emperor]
-
A.
emperor of China
The emperor of China was the supreme hereditary ruler of imperial China, regarded as the Son of Heaven and the ultimate political, military, and ritual authority over the Chinese empire.
-
B.
prince of the Empire of Japan
A prince of the Empire of Japan was a male member of the imperial family, typically born into or granted princely rank, who held hereditary status, court titles, and ceremonial or political roles within the pre-1947 Japanese imperial system.
-
C.
Empress of Japan
The Empress of Japan is the female consort or reigning sovereign of the Japanese imperial family, embodying ceremonial, cultural, and symbolic roles within the world’s oldest continuous hereditary monarchy.
-
D.
regent of Japan
A regent of Japan is an appointed official who governs on behalf of the emperor when the emperor is a minor, incapacitated, or otherwise unable to perform imperial duties.
-
E.
King of Anshan
The "King of Anshan" is a conceptual class representing the sovereign ruler of the ancient Elamite city-state of Anshan, embodying political authority, territorial control, and dynastic legitimacy within that historical context.
- 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_69bd4418390c8190b7e9766a2512ce55 |
completed | March 20, 2026, 12:56 p.m. |
Created at: March 20, 2026, 1:31 p.m.