Triple
T19626836
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Battle of Bhopal |
E471157
|
entity |
| Predicate | followedBy |
P78
|
FINISHED |
| Object | Treaty of Bhopal |
—
|
NE NERFINISHED |
How this triple was built (3 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: Treaty of Bhopal | Statement: [Battle of Bhopal, followedBy, Treaty of Bhopal]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Treaty of Bhopal Context triple: [Battle of Bhopal, followedBy, Treaty of Bhopal]
-
A.
Treaty of Rajghat
The Treaty of Rajghat was a peace agreement concluded during the Second Anglo-Maratha War that helped define British East India Company influence over Maratha territories in early 19th-century India.
-
B.
Treaty of Surji-Anjangaon
The Treaty of Surji-Anjangaon was a 1803 agreement between the British East India Company and the Maratha Empire that significantly expanded British control in central India during the Second Anglo-Maratha War.
-
C.
Treaty of Allahabad
The Treaty of Allahabad was a 1765 agreement that marked the formal beginning of British political control in India by granting the East India Company revenue-collecting rights (Diwani) over Bengal, Bihar, and Orissa.
-
D.
Treaty of Madras
The Treaty of Madras was a 1769 peace agreement between the Kingdom of Mysore and the British East India Company that ended the First Anglo-Mysore War and restored the pre-war status quo in southern India.
-
E.
Treaty of Deogaon
The Treaty of Deogaon was an 1803 agreement between the British East India Company and the Bhonsle ruler of Nagpur that ceded large territories, including parts of Orissa, to British control during the Second Anglo-Maratha War.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Treaty of Bhopal Target entity description: The Treaty of Bhopal was an 18th-century agreement that concluded the Battle of Bhopal, marking a significant shift in power between the Maratha Empire and the Mughal-aligned forces in central India.
-
A.
Treaty of Rajghat
The Treaty of Rajghat was a peace agreement concluded during the Second Anglo-Maratha War that helped define British East India Company influence over Maratha territories in early 19th-century India.
-
B.
Treaty of Surji-Anjangaon
The Treaty of Surji-Anjangaon was a 1803 agreement between the British East India Company and the Maratha Empire that significantly expanded British control in central India during the Second Anglo-Maratha War.
-
C.
Treaty of Allahabad
The Treaty of Allahabad was a 1765 agreement that marked the formal beginning of British political control in India by granting the East India Company revenue-collecting rights (Diwani) over Bengal, Bihar, and Orissa.
-
D.
Treaty of Madras
The Treaty of Madras was a 1769 peace agreement between the Kingdom of Mysore and the British East India Company that ended the First Anglo-Mysore War and restored the pre-war status quo in southern India.
-
E.
Treaty of Deogaon
The Treaty of Deogaon was an 1803 agreement between the British East India Company and the Bhonsle ruler of Nagpur that ceded large territories, including parts of Orissa, to British control during the Second Anglo-Maratha War.
- F. None of above. chosen
Provenance (2 batches)
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_69d8e511f28481909f4bc3ea9191e54a |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640eadcc48190ab5e36ddcde0c328 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:44 p.m.