Triple
T5113402
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bolpur subdivision |
E115270
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subdivision of a district in India |
C17604
|
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: subdivision of a district in India Context triple: [Bolpur subdivision, instanceOf, subdivision of a district in India]
-
A.
administrative district of India
An administrative district of India is a territorial subdivision of a state or union territory, governed by district-level authorities to manage local administration, law and order, and development activities.
-
B.
district of British India
A district of British India was an administrative subdivision governed by colonial authorities, typically comprising multiple towns and villages, used for managing revenue collection, law and order, and local governance under the British Raj.
-
C.
regulatory subdivision
A regulatory subdivision is a defined geographic or administrative area within a jurisdiction established for the purpose of applying, enforcing, or managing specific regulations, policies, or legal requirements.
-
D.
region of India
A region of India is a geographically and culturally distinct area within the country, often defined by shared historical, linguistic, economic, or administrative characteristics.
-
E.
regional division
A regional division is an organizational unit that segments a larger geographic area into distinct regions for administrative, operational, or strategic management purposes.
- 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_69bd4441d1648190a54a533895041987 |
completed | March 20, 2026, 12:57 p.m. |
Created at: March 20, 2026, 1:41 p.m.