Triple

T16768346
Position Surface form Disambiguated ID Type / Status
Subject First Aceh Expedition E407526 entity
Predicate instanceOf P0 FINISHED
Object Dutch colonial military 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 military expedition
Context triple: [First Aceh Expedition, instanceOf, Dutch colonial military 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. Portuguese military campaign
    A Portuguese military campaign is a coordinated series of armed operations conducted by Portugal’s military forces to achieve specific strategic, political, or territorial objectives, often within a defined geographic area and time period.
  • C. United States Army expedition
    A United States Army expedition is a formally organized, often temporary military operation conducted by the U.S. Army beyond its usual garrison locations to achieve specific strategic, tactical, or exploratory objectives.
  • D. 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.
  • E. Spanish colonial war
    A Spanish colonial war is an armed conflict involving Spain’s efforts to conquer, control, or defend overseas territories within its colonial empire, typically against indigenous populations, rival European powers, or independence movements.
  • 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_69d8839174188190909f190097207065 completed April 10, 2026, 4:58 a.m.
Created at: April 10, 2026, 5:21 a.m.