Triple
T29338541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | State Executive Committees (India) |
E743975
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | state-level disaster management body |
C5073
|
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: state-level disaster management body Context triple: [State Executive Committees (India), instanceOf, state-level disaster management body]
-
A.
state administrative board
A state administrative board is a government-appointed body that oversees, regulates, and implements specific public policies or administrative functions within a state’s jurisdiction.
-
B.
state government agency
A state government agency is an official public organization established by a state to implement laws, deliver services, and administer specific policy areas within that state’s jurisdiction.
-
C.
emergency management agency
chosen
An emergency management agency is an organization responsible for preparing for, coordinating, and responding to natural or human-made disasters to protect people, property, and the environment.
-
D.
state-level auxiliary organization
A state-level auxiliary organization is a supportive entity operating within a specific state that assists a primary organization by coordinating regional activities, resources, and representation aligned with the parent body’s goals.
-
E.
state regulatory agency
A state regulatory agency is a government body at the state level responsible for creating, implementing, and enforcing rules and standards within specific sectors (such as utilities, health, or finance) to protect the public interest and ensure legal compliance.
- 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
Created at: April 28, 2026, 1:32 p.m.