Triple
T17087178
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandhawalia dynasty |
E414628
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Sikh royal dynasty |
C37467
|
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: Sikh royal dynasty Context triple: [Sandhawalia dynasty, instanceOf, Sikh royal dynasty]
-
A.
Sikh dynasty
chosen
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.
institution of the Sikh Empire
An institution of the Sikh Empire is an organized political, military, religious, or administrative body established under Sikh rule (c. 1799–1849) to govern, manage resources, uphold law, or promote Sikh cultural and spiritual life.
-
C.
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.
-
D.
Sikh prince
A Sikh prince is a male royal figure from a Sikh ruling family or lineage, traditionally responsible for leadership, protection of the community, and upholding Sikh religious and cultural values.
-
E.
Indian royal dynasty
An Indian royal dynasty is a hereditary ruling family or lineage that governed a specific region or kingdom in the Indian subcontinent, often characterized by distinct cultural, political, and architectural legacies.
- 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_69d886cef44c8190ba56c44b4e863e64 |
completed | April 10, 2026, 5:12 a.m. |
Created at: April 10, 2026, 5:35 a.m.