Triple
T36417473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Kawanakajima |
E897050
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sengoku period battle |
C34965
|
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: Sengoku period battle Context triple: [Battle of Kawanakajima, instanceOf, Sengoku period battle]
-
A.
battle of the Sengoku period
chosen
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.
-
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.
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.
faction in the Battle of Sekigahara
A faction in the Battle of Sekigahara is a coalition of samurai lords and their forces aligned under a common political and military leader, pursuing shared strategic goals in the decisive 1600 conflict for control of Japan.
-
E.
Sengoku-period person
A Sengoku-period person is an individual living in Japan’s Warring States era (c. 1467–1600), shaped by constant military conflict, shifting feudal allegiances, and the rise of powerful warlords.
- 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_69f76e54ce408190849acc3f7758937c |
completed | May 3, 2026, 3:48 p.m. |
Created at: May 3, 2026, 4:10 p.m.