Triple
T16527384
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Governing Council of FTII |
E401476
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | apex decision-making body |
C172
|
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: apex decision-making body Context triple: [Governing Council of FTII, instanceOf, apex decision-making body]
-
A.
governing body
chosen
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.
-
B.
military decision-making body
A military decision-making body is an organized group of authorized personnel responsible for analyzing strategic and tactical information, evaluating options, and issuing binding directives that guide military operations and policy.
-
C.
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.
-
D.
OSCE decision-making body
The OSCE decision-making body is the principal collective organ within the Organization for Security and Co-operation in Europe responsible for formulating, negotiating, and adopting political, security, and operational decisions by consensus among participating States.
-
E.
advisory body
An advisory body is a group of appointed or elected individuals that provides expert guidance, recommendations, and informed opinions to decision-makers without having formal authority to implement decisions.
- 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_69d883838abc8190bc79cb2d41733ce2 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:14 a.m.