Triple

T26826526
Position Surface form Disambiguated ID Type / Status
Subject shishaku (viscount) in the kazoku peerage E675388 entity
Predicate instanceOf P0 FINISHED
Object Japanese noble rank C31808 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 noble rank
Context triple: [shishaku (viscount) in the kazoku peerage, instanceOf, Japanese noble rank]
  • A. Imperial Japanese military rank
    Imperial Japanese military rank is a hierarchical designation used in the armed forces of the Empire of Japan to define authority, responsibility, and status among its military personnel.
  • B. Japanese order of merit
    A Japanese order of merit is a formal honor awarded by the Japanese government to individuals, both domestic and foreign, in recognition of distinguished achievements or service in fields such as public service, culture, or international relations.
  • C. member of the Japanese aristocracy chosen
    A member of the Japanese aristocracy is an individual belonging to the traditional noble class of Japan, historically holding hereditary titles, social prestige, and often political or ceremonial influence within the imperial or feudal hierarchy.
  • D. Japanese aristocratic family
    A Japanese aristocratic family is a high-ranking lineage traditionally associated with noble titles, courtly status, and inherited social prestige within Japan’s historical class system.
  • E. Japanese honorific name
    A Japanese honorific name is a personal name accompanied by a respectful suffix (such as -san, -sama, -kun, or -chan) that reflects the social relationship, status, and level of politeness between speaker and referent.
  • 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_69eee9b6b28481909332f83eb17e5170 completed April 27, 2026, 4:44 a.m.
Created at: April 27, 2026, 4:58 a.m.