Triple
T28559736
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Office of Analysis for Europe |
E723103
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | regional analytical unit |
C37330
|
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: regional analytical unit Context triple: [Office of Analysis for Europe, instanceOf, regional analytical unit]
-
A.
geospatial analysis unit
A geospatial analysis unit is a defined spatial entity (such as a grid cell, administrative area, or custom polygon) used as the fundamental unit for organizing, analyzing, and aggregating geographic data and spatial relationships.
-
B.
policy analysis unit
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.
-
C.
regional institute
A regional institute is an organization dedicated to education, research, or specialized services that primarily serves and addresses the needs of a specific geographic area or region.
-
D.
regulatory statistics unit
A regulatory statistics unit is a specialized team that applies statistical methods to support regulatory decision-making, compliance evaluation, and policy development by analyzing and interpreting relevant data.
-
E.
regional intelligence formation
chosen
Regional intelligence formation is the process by which localized knowledge, data, and contextual insights are gathered, synthesized, and structured within a specific geographic or cultural area to support informed decision-making and strategic action.
- 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_69f01a60204481909af1bb76247b8221 |
completed | April 28, 2026, 2:24 a.m. |
Created at: April 28, 2026, 3:48 a.m.