Triple
T36417601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kantō Kanrei |
E897053
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | shogunal office |
C4989
|
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: shogunal office Context triple: [Kantō Kanrei, instanceOf, shogunal office]
-
A.
Japanese imperial office
A Japanese imperial office is a governmental or court position within the historical or modern Japanese imperial system, responsible for specific administrative, ceremonial, or advisory functions under the authority of the Emperor.
-
B.
imperial court office
chosen
An imperial court office is an administrative position or bureau within an empire’s central government responsible for managing specific functions of state, such as finance, justice, ceremony, or military affairs, under the authority of the sovereign.
-
C.
former shogunal residence
A former shogunal residence is a historic estate or palace that once served as the official home and administrative center of a shogun, reflecting the political power and cultural aesthetics of Japan’s feudal military government.
-
D.
Chamber of Princes
The Chamber of Princes was an advisory body established in British India in 1921 to represent the interests and opinions of the rulers of the princely states to the colonial government.
-
E.
bakufu official
A bakufu official is a government administrator serving under Japan’s shogunate, responsible for implementing the shogun’s policies, managing regional or central affairs, and maintaining order within the feudal military government.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.