Triple
T36106155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Heiji no ran |
E1044361
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | samurai conflict |
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 conflict Context triple: [Heiji no ran, instanceOf, samurai conflict]
-
A.
samurai rebellion
chosen
A samurai rebellion is an organized uprising by warrior elites against established authority, driven by conflicts over honor, power, or social order.
-
B.
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.
-
C.
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.
-
D.
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.
-
E.
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.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:08 p.m.