Triple
T6780024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bali expeditions |
E155655
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch colonial military campaign |
C21270
|
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: Dutch colonial military campaign Context triple: [Bali expeditions, instanceOf, Dutch colonial military campaign]
-
A.
Javanese military campaign
A Javanese military campaign is a coordinated series of armed operations conducted by Javanese polities or forces to achieve specific political, territorial, or strategic objectives.
-
B.
Dutch–Native American conflict
Dutch–Native American conflict refers to the series of violent and diplomatic confrontations between Dutch colonists and Indigenous peoples in North America during the 17th century, driven by competition over land, trade, and political control.
-
C.
Mughal campaign
A Mughal campaign is a military expedition undertaken by the Mughal Empire to expand, consolidate, or defend its territories through organized warfare and strategic operations.
-
D.
battle of the Franco-Dutch War
A battle of the Franco-Dutch War is a military engagement fought between 1672 and 1678 involving France and its allies against the Dutch Republic and its shifting coalition of European powers, typically characterized by complex political motives and evolving alliances.
-
E.
Dutch colony
A Dutch colony is a territory politically and economically controlled by the Netherlands, established primarily for trade, resource extraction, and strategic influence during the era of European imperial expansion.
- 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_69c688162bf8819088b664b5c3b5be7a |
completed | March 27, 2026, 1:37 p.m. |
Created at: March 27, 2026, 2:14 p.m.