Triple
T2311434
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | COBRA (Cabinet Office Briefing Rooms) |
E51965
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | government crisis response committee |
C1999
|
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: government crisis response committee Context triple: [COBRA (Cabinet Office Briefing Rooms), instanceOf, government crisis response committee]
-
A.
government committee
chosen
A government committee is a formally established group of officials or representatives tasked with studying specific issues, developing recommendations, and overseeing particular areas of public policy or administration.
-
B.
crisis-management mandate
A crisis-management mandate is a formal directive that defines the authority, responsibilities, and procedures an organization must follow to prepare for, respond to, and recover from critical incidents or emergencies.
-
C.
governing council
A governing council is a formal body of appointed or elected individuals responsible for making high-level decisions, setting policies, and providing oversight for an organization, community, or institution.
-
D.
crisis
A crisis is a critical turning point or period of intense difficulty and instability that demands urgent decision-making and action to prevent severe negative consequences.
-
E.
civil affairs unit
A civil affairs unit is a military organization responsible for managing relationships and coordination between armed forces and civilian populations, authorities, and institutions in areas of operation.
- 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_69a88b0bb30c81908ded03b006d29387 |
completed | March 4, 2026, 7:42 p.m. |
Created at: March 4, 2026, 7:49 p.m.