Triple
T20918971
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akizuki Rebellion |
E515150
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | samurai rebellion |
C43921
|
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: samurai rebellion Context triple: [Akizuki Rebellion, instanceOf, samurai rebellion]
-
A.
samurai clan
A samurai clan is a hereditary warrior lineage in feudal Japan, bound by loyalty, shared ancestry, and strict codes of honor, often controlling land, military power, and political influence.
-
B.
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.
-
C.
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.
-
D.
baronial rebellion
A baronial rebellion is an organized uprising by feudal barons or nobles against their sovereign, typically to resist royal authority, protect privileges, or force political concessions.
-
E.
revolutionary revolt
A revolutionary revolt is a collective, often radical uprising aimed at overthrowing an existing political or social order to establish a fundamentally new system.
- F. None of above. chosen
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_69e0b4f9d5ec8190bb2bd27350ed341c |
completed | April 16, 2026, 10:07 a.m. |
Created at: April 16, 2026, 12:48 p.m.