Triple
T21454478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nashik division |
E529305
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | division of Maharashtra |
C44789
|
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: division of Maharashtra Context triple: [Nashik division, instanceOf, division of Maharashtra]
-
A.
division of Haryana
A division of Haryana is an administrative unit comprising multiple districts within the Indian state of Haryana, established to facilitate regional governance and coordination of state functions.
-
B.
division of Hyderabad State
A division of Hyderabad State is an administrative subdivision that grouped several districts within the former princely state (and later Indian state) of Hyderabad for governance and revenue administration.
-
C.
division of Bihar
A division of Bihar is an administrative unit within the Indian state of Bihar that groups several districts under a divisional headquarters for coordinated governance and administration.
-
D.
division of British India
A division of British India was an administrative subdivision of a province, grouping several districts under a divisional commissioner for more efficient colonial governance and control.
-
E.
subdivision of a district in India
A subdivision of a district in India is an administrative unit below the district level that groups several tehsils or blocks to facilitate local governance, revenue administration, and public service delivery.
- 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_69e0c457579481909db68053ed99750c |
completed | April 16, 2026, 11:13 a.m. |
Created at: April 16, 2026, 6:07 p.m.