Triple
T938022
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince Masahito, Prince Hitachi |
E20241
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese prince |
C3248
|
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 prince Context triple: [Prince Masahito, Prince Hitachi, instanceOf, Japanese prince]
-
A.
member of the Japanese imperial family
chosen
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
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.
prince
A prince is a male royal family member, typically the son or close relative of a monarch, who may hold a hereditary or courtesy title and stand in line to the throne.
-
D.
English prince
An English prince is a male member of the British royal family, typically a son or close male-line descendant of the monarch, who holds the title of "Prince" and may perform ceremonial, diplomatic, and public duties on behalf of the Crown.
-
E.
Scottish prince
A Scottish prince is a male royal family member of Scotland, typically in the line of succession to the Scottish throne and bearing titles and duties associated with Scottish nobility and governance.
- 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_69a493b0270c81909e6c9ce310f6aa55 |
completed | March 1, 2026, 7:29 p.m. |
Created at: March 1, 2026, 7:40 p.m.