Triple
T2477243
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Higashifushimi Yorihito |
E55117
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese imperial prince |
C1555
|
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 prince Context triple: [Prince Higashifushimi Yorihito, instanceOf, Japanese imperial prince]
-
A.
member of the Japanese imperial family
A member of the Japanese imperial family is an individual related by blood or adoption to the Emperor of Japan, holding a formal status defined by the Imperial Household Law and participating in ceremonial, cultural, and representational duties of the monarchy.
-
B.
royal prince
chosen
A royal prince is a male member of a monarchy’s ruling family, typically in the line of succession to the throne and bearing ceremonial, diplomatic, and sometimes administrative duties.
-
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.
former Empress of Japan
A former Empress of Japan is a woman who previously held the title of Empress as the wife or consort of a reigning Japanese Emperor and has since left the position due to the Emperor’s abdication or death.
-
E.
Indian monarch
An Indian monarch is a sovereign ruler of a historical or contemporary Indian kingdom or empire, exercising supreme political and ceremonial authority within their realm.
- 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_69ab49e279e88190ab10d7248aea9d11 |
completed | March 6, 2026, 9:40 p.m. |
Created at: March 6, 2026, 9:45 p.m.