Triple
T28400965
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RA I management group |
E719392
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | leadership and coordination body |
C14661
|
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: leadership and coordination body Context triple: [RA I management group, instanceOf, leadership and coordination body]
-
A.
senior leadership body
A senior leadership body is a group of high-level executives or officials responsible for setting strategic direction, making key organizational decisions, and overseeing overall performance and governance.
-
B.
governing body
A governing body is an organized group of individuals with the authority and responsibility to make decisions, set policies, and oversee the direction and management of an institution, community, or state.
-
C.
intelligence coordination body
An intelligence coordination body is an organization responsible for integrating, harmonizing, and directing the activities, information sharing, and strategic priorities of multiple intelligence agencies or units to support national or organizational security objectives.
-
D.
coordination office
chosen
A coordination office is an organizational unit responsible for planning, aligning, and overseeing activities, resources, and communication among different stakeholders to ensure smooth and efficient execution of projects or operations.
-
E.
secretariat-type body
A secretariat-type body is an administrative organization that provides ongoing coordination, support, and implementation services for a larger governing or decision-making entity.
- 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_69eff6efd1b08190ae3cefd4f11388a2 |
completed | April 27, 2026, 11:53 p.m. |
Created at: April 28, 2026, 1:20 a.m.