Triple
T12286559
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Earl of Willingdon |
E292842
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | governor-general of India |
C5324
|
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: governor-general of India Context triple: [The Earl of Willingdon, instanceOf, governor-general of India]
-
A.
Governor-General of Bengal
The Governor-General of Bengal was the chief British official in colonial Bengal, later evolving into the de facto head of British administration in India, responsible for overseeing governance, revenue, and foreign affairs in the region.
-
B.
governor-general
chosen
A governor-general is the representative of a monarch in a constitutional monarchy, performing ceremonial duties and certain constitutional functions on the monarch’s behalf within a specific country or territory.
-
C.
Vicereine of India
The Vicereine of India was the wife of the British Viceroy of India, serving as the highest-ranking female figure in the colonial administration and often playing a prominent role in social, charitable, and ceremonial affairs.
-
D.
governor-general of the Dutch East Indies
The governor-general of the Dutch East Indies was the highest colonial official representing the Dutch crown, responsible for governing and administering the territories of the Dutch East Indies.
-
E.
Governor of Madras
The Governor of Madras was the chief colonial administrator of the Madras Presidency under British rule in India, responsible for overseeing governance, law, and policy implementation in the region.
- 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_69d6ab690ad081908c0ed3870ec82d53 |
completed | April 8, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:52 p.m.