Triple
T24831816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Third Dutch expedition to Bali (1849) |
E621359
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Dutch colonial expedition |
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 expedition Context triple: [Third Dutch expedition to Bali (1849), instanceOf, Dutch colonial expedition]
-
A.
Dutch colonial military campaign
chosen
A Dutch colonial military campaign is an organized series of armed operations conducted by the Netherlands to conquer, pacify, or control territories and populations within its overseas empire.
-
B.
Age of Discovery expedition
An Age of Discovery expedition is a state- or crown-sponsored maritime voyage undertaken between the 15th and 17th centuries to explore unknown regions, establish trade routes, claim territories, and gather scientific and geographic knowledge.
-
C.
Russian naval expedition
A Russian naval expedition is a state-organized maritime operation undertaken by the Russian Navy for purposes such as exploration, power projection, military engagement, or strategic presence beyond home waters.
-
D.
Dutch trading post
A Dutch trading post is a commercial outpost established by the Dutch, primarily during the 17th and 18th centuries, to facilitate trade, resource extraction, and colonial administration in foreign territories.
-
E.
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.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:15 a.m.