Triple
T7308173
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pratapgarh district, Uttar Pradesh |
E168028
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | district of Uttar Pradesh |
C14433
|
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: district of Uttar Pradesh Context triple: [Pratapgarh district, Uttar Pradesh, instanceOf, district of Uttar Pradesh]
-
A.
administrative district of India
chosen
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.
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.
-
C.
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.
-
D.
state of India
A state of India is a primary administrative and political subdivision of the country, each with its own government, legislature, and defined territorial boundaries under the Indian Constitution.
-
E.
populated place in Madhya Pradesh
A populated place in Madhya Pradesh is any city, town, village, or settlement within the Indian state of Madhya Pradesh where people live and carry out social, economic, and cultural activities.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
Created at: March 27, 2026, 3:01 p.m.