Triple
T7649267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince of Asaka |
E173204
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese imperial title |
C15552
|
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: Japanese imperial title Context triple: [Prince of Asaka, instanceOf, Japanese imperial title]
-
A.
Japanese monarch
A Japanese monarch is the hereditary sovereign of Japan, traditionally regarded as a symbolic and unifying figurehead of the nation and its people.
-
B.
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.
-
C.
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.
-
D.
prince of the Empire of Japan
chosen
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.
-
E.
Russian imperial title
A Russian imperial title is a formal designation of rank and authority within the hierarchy of the Russian Empire, used by monarchs, nobility, and high officials to signify their status and governing roles.
- 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_69c6995473348190a4f41d110d619a18 |
completed | March 27, 2026, 2:51 p.m. |
Created at: March 27, 2026, 3:58 p.m.