Triple
T16608395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lahore Darbar |
E403503
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | institution of the Sikh Empire |
C38103
|
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: institution of the Sikh Empire Context triple: [Lahore Darbar, instanceOf, institution of the Sikh Empire]
-
A.
Sikh dynasty
The Sikh dynasty refers to the ruling lineage and political establishment founded by Maharaja Ranjit Singh in the early 19th century, which unified much of the Punjab region into a powerful Sikh Empire before its annexation by the British.
-
B.
Indian empire
The Indian empire is a vast, historically rich civilization-state encompassing diverse cultures, religions, and political entities that have risen and fallen across the Indian subcontinent over millennia.
-
C.
subah of the Mughal Empire
A subah of the Mughal Empire was a major provincial administrative division governed by a subahdar, responsible for local governance, revenue collection, and military control within its territory.
-
D.
Bengal dynasty
The Bengal dynasty refers to the succession of ruling families and political powers that governed the Bengal region (in present-day Bangladesh and eastern India) across various historical periods, shaping its cultural, economic, and political development.
-
E.
Mughal–Rajput relations
Mughal–Rajput relations refer to the complex web of political alliances, military conflicts, matrimonial ties, and cultural exchanges between the Mughal Empire and the Rajput kingdoms of northern and western India from the 16th to 18th centuries.
- 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_69d883880d0c81908b5fcd454e767b60 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:17 a.m.