Triple

T18151390
Position Surface form Disambiguated ID Type / Status
Subject Fujiwara no Inshi E434510 entity
Predicate instanceOf P0 FINISHED
Object member of Fujiwara clan 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: member of Fujiwara clan
Context triple: [Fujiwara no Inshi, instanceOf, member of Fujiwara clan]
  • A. Fujiwara clan member chosen
    A Fujiwara clan member is an aristocrat belonging to the powerful Fujiwara family of classical Japan, whose political influence peaked in the Heian period through strategic court positions and marital alliances with the imperial line.
  • B. 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.
  • C. 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.
  • 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. 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.
  • 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_69d8b90aac308190801e2c57d8c5bfe5 completed April 10, 2026, 8:47 a.m.
Created at: April 10, 2026, 10:29 a.m.