Triple
T27751768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jaisalmer royal lineage |
E701229
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Indian princely lineage |
C30465
|
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: Indian princely lineage Context triple: [Jaisalmer royal lineage, instanceOf, Indian princely lineage]
-
A.
Indian royal dynasty
chosen
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.
-
B.
Hindu royal lineage
A Hindu royal lineage is a hereditary line of rulers and nobles within Hindu society, traditionally legitimized by sacred texts, divine ancestry, and ritual authority.
-
C.
Rajput princely state
A Rajput princely state was a semi-autonomous, monarch-ruled territory in the Indian subcontinent governed by a Rajput dynasty under the suzerainty of larger empires such as the Mughals or the British Crown.
-
D.
Indian princely ruler
An Indian princely ruler is a hereditary monarch or sovereign of a semi-autonomous princely state in the Indian subcontinent who exercised varying degrees of internal authority under overarching imperial or colonial powers.
-
E.
South Indian royal dynasty
A South Indian royal dynasty is a hereditary ruling family that governed regions of southern India, shaping its political structures, culture, religion, and art over successive generations.
- 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_69ef6a5193808190816eb7d0020b2d87 |
completed | April 27, 2026, 1:53 p.m. |
Created at: April 27, 2026, 4:20 p.m.