Triple
T27707613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Standing Committee on Standards Implementation |
E698595
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | FSB body |
C53189
|
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: FSB body Context triple: [Standing Committee on Standards Implementation, instanceOf, FSB body]
-
A.
foreign and security policy body
A foreign and security policy body is an institutional entity responsible for formulating, coordinating, and overseeing a state’s external relations and national security strategies, including diplomacy, defense, and international cooperation.
-
B.
EU–US body
A formal, institutionalized entity that facilitates structured political, economic, and regulatory dialogue and cooperation between the European Union and the United States.
-
C.
state body of the Russian Federation
A state body of the Russian Federation is an official public authority established by the Constitution or federal law, empowered to exercise legislative, executive, or judicial functions within the Russian state system.
-
D.
organ of the European Systemic Risk Board
An organ of the European Systemic Risk Board is a formal institutional body within the ESRB’s governance structure that performs specific functions related to the identification, assessment, and mitigation of systemic risks to the EU financial system.
-
E.
CSTO body
A CSTO body is an organizational unit within the Collective Security Treaty Organization responsible for coordinating and implementing specific aspects of the alliance’s collective defense, security policies, and cooperative activities among member states.
- F. None of above. chosen
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_69ef590f655c81909f93893b3b3219b2 |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 3 p.m.