Triple
T38030070
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dhundhar region |
E948883
|
entity |
| Predicate | includesFormerPrincelyState |
—
|
GENERATED |
| Object | Jaipur State |
—
|
UNRECOGNIZED GENERATED |
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includesFormerPrincelyState Context triple: [Dhundhar region, includesFormerPrincelyState, Jaipur State]
-
A.
containsFormerPrincelyState
chosen
Indicates that a geopolitical entity includes within its boundaries an area that was once a princely state.
-
B.
laterPrincelyState
Indicates that an entity subsequently became or was recognized as a princely state at a later historical period.
-
C.
notablePrincelyState
Indicates that an entity is recognized as a historically significant princely state, typically within a larger imperial or colonial framework.
-
D.
princelyStateCategory
Indicates that an entity is classified as belonging to the category of princely states.
-
E.
princelyStateName
Indicates that an entity has the name of a princely state (a semi-autonomous, traditionally monarch-ruled territory).
- 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_69f76efd1bc48190a729097fe5177b61 |
completed | May 3, 2026, 3:51 p.m. |
Created at: May 3, 2026, 4:20 p.m.