Triple
T11096913
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European Globalisation Adjustment Fund |
E262400
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | labour market adjustment fund |
C21079
|
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: labour market adjustment fund Context triple: [European Globalisation Adjustment Fund, instanceOf, labour market adjustment fund]
-
A.
labor market reform
Labor market reform is the process of changing laws, regulations, and institutions governing employment to improve efficiency, flexibility, equity, or job creation in an economy.
-
B.
labour market coordination mechanism
A labour market coordination mechanism is the set of institutions, rules, and practices through which employers, workers, and the state align wage-setting, employment conditions, and labour allocation across the economy.
-
C.
stabilization fund
chosen
A stabilization fund is a reserve of financial resources established by a government or organization to smooth out economic fluctuations, stabilize revenues or prices, and provide a buffer against external shocks.
-
D.
labor relations board
A labor relations board is a governmental or quasi-judicial body that oversees and enforces laws governing collective bargaining, union representation, and the resolution of labor-management disputes.
-
E.
planned regional monetary fund
A planned regional monetary fund is a proposed financial institution designed to pool resources from member countries within a specific region to provide monetary stability, balance-of-payments support, and coordinated economic policies.
- 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_69d6aa9a40d88190a373e2c7e48285db |
completed | April 8, 2026, 7:20 p.m. |
Created at: April 8, 2026, 9:27 p.m.