Triple
T18447097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Government of National Capital Territory of Delhi and Government of India (through DMRC) |
E450683
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | joint administrative arrangement |
C32722
|
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: joint administrative arrangement Context triple: [Government of National Capital Territory of Delhi and Government of India (through DMRC), instanceOf, joint administrative arrangement]
-
A.
joint management arrangement
A joint management arrangement is a structured agreement in which two or more parties share authority, responsibilities, and decision-making over a specific resource, project, or organization.
-
B.
interagency coordination arrangement
chosen
An interagency coordination arrangement is a structured agreement or framework that defines how multiple government or organizational agencies collaborate, share information, and align responsibilities to achieve common objectives.
-
C.
interagency committee
An interagency committee is a collaborative body composed of representatives from multiple government agencies formed to coordinate policies, share information, and address cross-cutting issues.
-
D.
intergovernmental coordination agency
An intergovernmental coordination agency is an organization formed by multiple governments to align policies, share information, and manage joint initiatives across jurisdictions.
-
E.
administrative establishment
An administrative establishment is an organization or facility responsible for managing, coordinating, and executing governmental or institutional policies, procedures, and services.
- 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_69d8d38345688190b565eac2e4cd7935 |
completed | April 10, 2026, 10:40 a.m. |
Created at: April 10, 2026, 11:30 a.m.