Triple

T17889029
Position Surface form Disambiguated ID Type / Status
Subject Indian subcontinent campaigns E447266 entity
Predicate instanceOf P0 FINISHED
Object British colonial military operation C40015 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: British colonial military operation
Context triple: [Indian subcontinent campaigns, instanceOf, British colonial military operation]
  • A. Dutch colonial military campaign
    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. Royal Navy operation
    A Royal Navy operation is a coordinated maritime mission or campaign conducted by the United Kingdom’s naval forces to achieve specific military, security, or humanitarian objectives at sea or in littoral environments.
  • C. British colonial regiment
    A British colonial regiment is a military unit raised, organized, and commanded by the British Empire from its overseas colonies, typically composed of local recruits led by British officers to serve imperial defense and expansion.
  • D. 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.
  • E. British colonial position
    A British colonial position is an official role or office established by the British Empire to administer, govern, or oversee territories and populations under colonial rule.
  • 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_69d8b9f59bd48190a6fc925a855b8bac completed April 10, 2026, 8:51 a.m.
Created at: April 10, 2026, 10:18 a.m.