Triple
T14572505
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osaka no Eki |
E341953
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of the Sengoku period |
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: battle of the Sengoku period Context triple: [Osaka no Eki, instanceOf, battle of the Sengoku period]
-
A.
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.
-
B.
Japanese war
Japanese war is a conceptual class representing organized, large-scale armed conflicts involving Japan, encompassing their political causes, military strategies, cultural impacts, and historical consequences.
-
C.
Japanese invasions of Korea
The Japanese invasions of Korea (1592–1598) were a series of military campaigns launched by Toyotomi Hideyoshi’s Japan to conquer the Korean Peninsula and ultimately invade Ming China, resulting in widespread devastation, fierce resistance by Korean and Ming forces, and a prolonged regional conflict.
-
D.
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.
-
E.
battle of the Italian Wars
A battle of the Italian Wars is a military engagement fought between 1494 and 1559 among major European powers over control of the Italian peninsula, typically involving shifting alliances, evolving tactics, and significant political consequences.
- 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_69d822dcc6248190bed689984bceb0e2 |
completed | April 9, 2026, 10:06 p.m. |
Created at: April 10, 2026, 1:24 a.m.