Triple
T24645202
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Anegawa |
E610088
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sengoku-period conflict |
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 conflict Context triple: [Battle of Anegawa, instanceOf, Sengoku-period conflict]
-
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.
16th-century conflict
A 16th-century conflict is a historically documented military, political, or religious struggle that occurred between 1501 and 1600, involving organized groups or states and significantly influencing the social and geopolitical landscape of the early modern period.
-
D.
period of warfare
A period of warfare is a span of time characterized by sustained armed conflict between organized groups, typically involving military operations, political objectives, and significant social and economic disruption.
-
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_69e2c4d350a481909170482bc2ce6af9 |
completed | April 17, 2026, 11:40 p.m. |
Created at: April 18, 2026, 2:33 a.m.