Triple
T3116502
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Mukden |
E65074
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engagement of the Russo-Japanese War |
C12247
|
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: engagement of the Russo-Japanese War Context triple: [Battle of Mukden, instanceOf, engagement of the Russo-Japanese War]
-
A.
engagement of the Falklands War
The engagement of the Falklands War is a military operation or battle between British and Argentine forces during the 1982 conflict over the Falkland Islands, characterized by specific objectives, participating units, tactics, and outcomes within the broader campaign.
-
B.
Pacific War engagement
A Pacific War engagement is a specific military confrontation between opposing forces in the Pacific theater during World War II, encompassing actions in air, sea, and/or land domains.
-
C.
engagement of the Nine Years' War
An engagement of the Nine Years' War is a specific military confrontation—such as a battle, siege, raid, or skirmish—fought between the war’s opposing coalitions within the broader 1688–1697 conflict.
-
D.
engagement of the French Revolutionary Wars
An engagement of the French Revolutionary Wars is a specific military clash—ranging from small skirmishes to major battles—fought between Revolutionary France and its opponents between 1792 and 1802.
-
E.
imperial war
Imperial war is a large-scale, often expansionist conflict waged by an empire to acquire, control, or maintain dominance over territories, peoples, or resources beyond its original borders.
- 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_69ad857fcc088190b0c4d45a5cde6f61 |
completed | March 8, 2026, 2:19 p.m. |
Created at: March 8, 2026, 3:04 p.m.