Triple
T22382437
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Forty-seven Ronin incident |
E553308
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Edo-period incident |
C21713
|
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 incident Context triple: [Forty-seven Ronin incident, instanceOf, Edo-period incident]
-
A.
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.
-
B.
Japanese historical event
chosen
A Japanese historical event is a significant occurrence in Japan’s past—such as a political shift, conflict, cultural transformation, or natural disaster—that notably influenced the nation’s society, governance, or cultural development.
-
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.
battle of the Genpei War
A battle of the Genpei War is a specific military engagement between the Taira and Minamoto clans during Japan’s 1180–1185 civil conflict, characterized by its participants, location, tactics, outcome, and impact on the war’s progression.
-
E.
battle of the Sengoku period
A battle of the Sengoku period is a military engagement fought between rival feudal lords in Japan (c. 1467–1600), characterized by shifting alliances, samurai warfare, and struggles for territorial and political dominance.
- 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_69e11e4c03248190a26a5060ea6973ee |
completed | April 16, 2026, 5:37 p.m. |
Created at: April 16, 2026, 8:45 p.m.