Triple
T16695818
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fujiwara no Kaneie |
E405712
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Fujiwara clan member |
C38251
|
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: Fujiwara clan member Context triple: [Fujiwara no Kaneie, instanceOf, Fujiwara clan member]
-
A.
member of the Kujō family
A member of the Kujō family is an individual belonging to the historically influential Japanese aristocratic lineage associated with the Fujiwara clan and the regent houses of the Heian and Kamakura periods.
-
B.
member of the Minamoto clan
A member of the Minamoto clan is an individual belonging to a powerful and prestigious samurai lineage in Japan, historically influential in politics, warfare, and the establishment of the shogunate.
-
C.
member of the Tokugawa clan
A member of the Tokugawa clan is an individual belonging to the powerful samurai family that established and ruled Japan’s Tokugawa shogunate from 1603 to 1868, holding significant political, military, and social influence.
-
D.
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.
-
E.
Ashikaga clan member
An Ashikaga clan member is an individual belonging to the powerful samurai family that founded and led Japan’s Ashikaga (Muromachi) shogunate from the 14th to 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_69d8838db21081909589220fd71440a4 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:19 a.m.