Triple
T17587473
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Union economics |
E428362
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | subfield of regional economics |
C20041
|
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: subfield of regional economics Context triple: [European Union economics, instanceOf, subfield of regional economics]
-
A.
regional economic zone
A regional economic zone is a geographically defined area within or across countries where economic policies, regulations, and incentives are coordinated to promote trade, investment, and development.
-
B.
subfield of human geography
A subfield of human geography is a specialized area of study that focuses on particular aspects of the relationships between people and their environments, such as cultural patterns, economic activities, political organization, or urban development.
-
C.
applied economics field
chosen
An applied economics field is a branch of economics that uses economic theories, data, and quantitative methods to analyze and solve real-world problems in specific sectors or policy areas.
-
D.
economics research series
A structured collection of scholarly works, often published periodically, that presents original research, analyses, and findings on topics within the field of economics.
-
E.
monetary policy region
A monetary policy region is a geographic or economic area within which a single monetary authority implements a unified set of monetary policy tools and rules, typically sharing a common currency and interest rate framework.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
Created at: April 10, 2026, 5:51 a.m.