Triple
T4798449
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kuni no miya Kuniyoshi |
E106772
|
entity |
| Predicate | memberOf |
P10
|
FINISHED |
| Object | House of Kuni |
E106772
|
NE FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: House of Kuni | Statement: [Kuni no miya Kuniyoshi, memberOf, House of Kuni]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: House of Kuni Context triple: [Kuni no miya Kuniyoshi, memberOf, House of Kuni]
-
A.
House of Kuni
chosen
The House of Kuni is a Japanese imperial noble family line to which Empress Kōjun belonged.
-
B.
House of Asaka
The House of Asaka was a collateral branch of Japan’s imperial family, founded by Prince Asaka Yasuhiko in the early 20th century.
-
C.
House of Akishino
The House of Akishino is a branch of Japan’s Imperial Family centered on Prince Fumihito, the Crown Prince of Japan, and his immediate descendants.
-
D.
House of Yi
The House of Yi was the royal family that ruled Korea for centuries, including during the final Korean Empire period before Japanese annexation.
-
E.
House of Jochi
The House of Jochi was the ruling dynasty descended from Jochi, eldest son of Genghis Khan, which governed major Mongol successor states such as the Golden Horde.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 batches)
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_69bd43f591c881909e5a532388b0f3f3 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd6633b02c8190994d4b3543220efa |
completed | March 20, 2026, 3:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69be4d9a76c08190bd19fcef378cd640 |
completed | March 21, 2026, 7:49 a.m. |
Created at: March 20, 2026, 1:22 p.m.