Triple
T4627441
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minamoto no Yoshitsune |
E101132
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | member of the Minamoto clan |
C16140
|
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: member of the Minamoto clan Context triple: [Minamoto no Yoshitsune, instanceOf, member of the Minamoto clan]
-
A.
member of the Jochid dynasty
A member of the Jochid dynasty is an individual descended from Jochi, the eldest son of Genghis Khan, belonging to the ruling lineage that governed the Golden Horde and related successor states.
-
B.
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.
-
C.
head of the Tokugawa family
The head of the Tokugawa family is the hereditary leader of the Tokugawa clan, historically serving as the shogun or principal patriarch guiding the family's political, social, and cultural legacy in Japan.
-
D.
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.
-
E.
member of the Rurik dynasty
A member of the Rurik dynasty is an individual belonging to the medieval ruling family traditionally traced to the Varangian prince Rurik, which governed parts of Eastern Europe, including Kievan Rus and later principalities, from the 9th to the 16th centuries.
- F. None of above. chosen
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_69bd43d0497c8190ac23c65c5804846a |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:13 p.m.