Triple
T36357488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kōshaku |
E895384
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Japanese peerage title |
C15547
|
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 peerage title Context triple: [Kōshaku, instanceOf, Japanese peerage title]
-
A.
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.
-
B.
peer of the Empire of Japan
chosen
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.
-
C.
member of the Japanese aristocracy
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 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.
-
E.
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.
- 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_69f76e5044248190b390d8887dc03254 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:09 p.m.