Triple
T19587235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BIS Monetary and Economic Department |
E434166
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | research and policy analysis arm |
C5451
|
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: research and policy analysis arm Context triple: [BIS Monetary and Economic Department, instanceOf, research and policy analysis arm]
-
A.
policy analysis unit
chosen
A policy analysis unit is an organizational entity responsible for systematically evaluating, comparing, and forecasting the impacts of public or institutional policies to inform evidence-based decision-making.
-
B.
public policy research institute
A public policy research institute is an organization that conducts independent, systematic analysis of public issues to inform and influence government decision-making and public debate.
-
C.
military analysis organization
A military analysis organization is an entity that systematically collects, evaluates, and interprets defense-related information to inform strategic, operational, and tactical decision-making.
-
D.
security studies institution
A security studies institution is an organization dedicated to researching, teaching, and advising on issues of national, international, and human security, including conflict, defense policy, intelligence, and strategic studies.
-
E.
policy bureau
A policy bureau is an organizational unit within a government or institution responsible for researching, developing, coordinating, and overseeing the implementation of policies in a specific domain.
- 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_69d8e510024481908415c0d616fa6186 |
completed | April 10, 2026, 11:54 a.m. |
Created at: April 10, 2026, 1:43 p.m.