Triple

T18555577
Position Surface form Disambiguated ID Type / Status
Subject Danish–Nayak treaty of 1620 E453494 entity
Predicate instanceOf P0 FINISHED
Object colonial-era agreement C383 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: colonial-era agreement
Context triple: [Danish–Nayak treaty of 1620, instanceOf, colonial-era agreement]
  • A. medieval political agreement
    A medieval political agreement is a formal or informal pact between rulers, nobles, or institutions that defines mutual obligations—such as protection, allegiance, tribute, or territorial control—within the feudal and dynastic power structures of the Middle Ages.
  • B. colonial legislature
    A colonial legislature is a representative governing body established in a colony to create laws, manage local affairs, and advise or balance the authority of the colonial governor and imperial power.
  • C. colonial governing charter
    A colonial governing charter is a formal legal document issued by a sovereign power that establishes the framework, authority, and rules by which a colony is organized and governed.
  • D. colonial-era event chosen
    A colonial-era event is a historically significant occurrence that took place during a period when one nation exercised political, economic, or cultural control over foreign territories and populations.
  • E. colonial order
    A colonial order is a hierarchical system of political, economic, and cultural domination in which an external power controls and structures the institutions, resources, and social relations of a colonized territory to serve imperial interests.
  • 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_69d8d388b0c881908e610a1c45b52640 completed April 10, 2026, 10:40 a.m.
Created at: April 10, 2026, 11:38 a.m.