Triple
T3769521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhenish capitalism |
E82762
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | coordinated market economy |
C542
|
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: coordinated market economy Context triple: [Rhenish capitalism, instanceOf, coordinated market economy]
-
A.
capitalist economy
chosen
A capitalist economy is an economic system in which private individuals and firms own the means of production and operate for profit within markets characterized by voluntary exchange, competition, and price signals.
-
B.
centralized economic planning system
A centralized economic planning system is a structure in which a central authority makes decisions about the allocation of resources, production targets, and distribution of goods and services across an economy.
-
C.
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.
-
D.
common market
A common market is an economic integration arrangement in which member countries remove internal trade barriers, adopt a common external tariff, and allow free movement of goods, services, capital, and labor among themselves.
-
E.
economic policy coordination tool
An economic policy coordination tool is a system that helps governments and institutions design, align, and monitor fiscal, monetary, and regulatory policies to achieve shared macroeconomic objectives.
- 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_69ad8b207b0081909d2b48843fbd8795 |
completed | March 8, 2026, 2:43 p.m. |
Created at: March 8, 2026, 3:35 p.m.