Triple
T3843402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naval Battle of Hakodate |
E93507
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | battle of the Boshin War |
C647
|
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 Boshin War Context triple: [Naval Battle of Hakodate, instanceOf, battle of the Boshin War]
-
A.
Act of the Diet of Japan
An Act of the Diet of Japan is a formal law enacted by Japan’s national legislature, consisting of the House of Representatives and the House of Councillors, through its prescribed legislative process.
-
B.
engagement of the Russo-Japanese War
An engagement of the Russo-Japanese War is a discrete military encounter—on land, sea, or both—between Russian and Japanese forces during the 1904–1905 conflict, characterized by specific participants, location, timeframe, and tactical objectives.
-
C.
battle of the Northwest Indian War
A battle of the Northwest Indian War is an armed military engagement between United States forces and a coalition of Native American nations fought in the Old Northwest between 1785 and 1795 as part of the struggle for control of the region.
-
D.
battle of the Nine Years' War
A battle of the Nine Years' War is a military engagement fought between 1688 and 1697 involving the Grand Alliance and France, characterized by early modern tactics, shifting coalitions, and the broader struggle for European balance of power.
-
E.
battles
chosen
Battles are organized, often large-scale armed conflicts between opposing forces, characterized by strategic maneuvers, tactical engagements, and the pursuit of specific military objectives within a defined time and place.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
Created at: March 9, 2026, 3:18 p.m.