Triple
T35479360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tozama domain |
E1025426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | political division in Edo-period Japan |
C21815
|
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: political division in Edo-period Japan Context triple: [tozama domain, instanceOf, political division in Edo-period Japan]
-
A.
administrative division of Japan
chosen
An administrative division of Japan is a geographically defined area, such as a prefecture, municipality, or special ward, established by the government to organize local governance, public administration, and the delivery of services.
-
B.
Bugis polity
A Bugis polity is a traditional socio-political entity of the Bugis people of South Sulawesi, typically organized around a kingdom or chiefdom with its own ruler, customary laws, and maritime-oriented economy and alliances.
-
C.
Heian-period conflict
A Heian-period conflict is a historically situated struggle or dispute in Japan’s Heian era (794–1185), involving political, military, or social tensions among imperial, aristocratic, and emerging warrior factions.
-
D.
Edo period institution
An Edo period institution is an organized social, political, economic, or cultural structure that operated in Japan between 1603 and 1868 under Tokugawa rule, shaping and regulating aspects of daily life and governance.
-
E.
Meiji-era policy
Meiji-era policy refers to the set of modernization and Westernization reforms implemented in Japan from 1868 to 1912 to centralize state power, industrialize the economy, and transform social, legal, and military institutions.
- 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_69f76dfadba0819083456aadcd6864ea |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:04 p.m.