Triple
T7065402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nagaoka Domain |
E164335
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Edo period domain |
C14196
|
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: Edo period domain Context triple: [Nagaoka Domain, instanceOf, Edo period domain]
-
A.
Edo period institution
chosen
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.
-
B.
Edo-period architecture
Edo-period architecture refers to the Japanese building styles from the early 17th to mid-19th centuries characterized by wooden construction, modular interiors, sliding doors, tatami flooring, and a balance of simplicity, functionality, and refined ornamentation seen in castles, temples, townhouses, and teahouses.
-
C.
Edo-period person
An Edo-period person is an individual living in Japan between 1603 and 1868, shaped by Tokugawa-era social hierarchies, cultural practices, and political stability.
-
D.
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.
-
E.
Bugis principality
A Bugis principality is a traditional political entity or small sovereign state historically governed by Bugis rulers in South Sulawesi, Indonesia, characterized by its own leadership, territory, and customary laws.
- 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_69c688796c148190adb2f1596f595f22 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 2:39 p.m.