Triple
T28129129
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ōjin |
E711013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | semi-legendary Japanese emperor |
C15982
|
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: semi-legendary Japanese emperor Context triple: [Ōjin, instanceOf, semi-legendary Japanese emperor]
-
A.
Jochid prince
A Jochid prince is a male royal descendant of Jochi, the eldest son of Genghis Khan, belonging to the Jochid lineage that ruled and influenced territories of the Golden Horde and related Mongol successor states.
-
B.
Japanese monarch
chosen
A Japanese monarch is the hereditary sovereign of Japan, traditionally regarded as a symbolic and unifying figurehead of the nation and its people.
-
C.
commoner-born empress consort of Japan
A commoner-born empress consort of Japan is a woman of non-aristocratic, non-imperial origin who marries the reigning emperor and assumes the formal role and duties of empress consort within the Japanese imperial household.
-
D.
Shunga ruler
A Shunga ruler is a monarch from the Shunga dynasty (c. 185–73 BCE) in ancient India, known for governing a post-Mauryan empire centered in northern and central India and for patronizing Brahmanical traditions and early art.
-
E.
Geatish king
A Geatish king is the sovereign ruler of the Geats, responsible for leading warriors in battle, upholding laws and customs, and ensuring the prosperity and protection of his people.
- 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_69ef9b73bd288190a21ae3d6aa14f386 |
completed | April 27, 2026, 5:22 p.m. |
Created at: April 27, 2026, 9:22 p.m.