Triple
T34505103
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | District Magistrate of East Champaran |
E885862
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | executive head of district administration |
C59858
|
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: executive head of district administration Context triple: [District Magistrate of East Champaran, instanceOf, executive head of district administration]
-
A.
executive head of province
The executive head of province is the highest-ranking official responsible for leading the provincial government, implementing laws and policies, and overseeing administration within the province.
-
B.
Executive Minister
An Executive Minister is a senior religious leader responsible for overseeing the administration, spiritual direction, and strategic governance of a church or denomination.
-
C.
regional directors
Regional directors are senior managers responsible for overseeing operations, strategy implementation, and performance across multiple locations within a defined geographic area.
-
D.
head of government office
The head of government office is an organizational unit that supports and coordinates the activities, decision-making, and administration of a jurisdiction’s chief executive (such as a prime minister or president) by providing policy advice, strategic planning, and operational management.
-
E.
district administration
District administration is the local governing and executive authority responsible for implementing government policies, managing public services, and coordinating development activities within a defined district.
- 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_69f349cc0220819081f154c6964f4dc2 |
completed | April 30, 2026, 12:23 p.m. |
Created at: May 1, 2026, 2:01 a.m.