Triple
T8561177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NDRF |
E202693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | federal disaster response force |
C15106
|
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: federal disaster response force Context triple: [NDRF, instanceOf, federal disaster response force]
-
A.
federation of government agencies
A federation of government agencies is a collaborative structure in which multiple semi-autonomous public organizations coordinate policies, resources, and operations to achieve shared governmental objectives while retaining their individual mandates.
-
B.
auxiliary military force
An auxiliary military force is a supplementary, often non-regular or part-time armed organization that supports a nation’s primary military through additional manpower, specialized skills, or local defense roles.
-
C.
defense organization
A defense organization is an entity, typically governmental or intergovernmental, responsible for planning, coordinating, and executing activities to protect a nation or group of nations from military and security threats.
-
D.
crisis response organization
chosen
A crisis response organization is an entity that rapidly coordinates resources, personnel, and communication to assess, manage, and mitigate emergencies or disasters affecting people, infrastructure, or the environment.
-
E.
firefighting organization
A firefighting organization is a coordinated group responsible for preventing, controlling, and extinguishing fires, as well as responding to related emergencies to protect life, property, and the environment.
- 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_69ca8326e6c881908ff720d6abaebdc5 |
completed | March 30, 2026, 2:05 p.m. |
Created at: March 30, 2026, 6:20 p.m.