Triple
T31216314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Empirical studies of the New Jersey–Pennsylvania minimum wage experiment |
E795880
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | minimum wage policy evaluation |
C39245
|
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: minimum wage policy evaluation Context triple: [Empirical studies of the New Jersey–Pennsylvania minimum wage experiment, instanceOf, minimum wage policy evaluation]
-
A.
labor economics study
chosen
A labor economics study analyzes how workers, employers, and institutions interact in labor markets to determine wages, employment, and working conditions.
-
B.
labor supply elasticity
Labor supply elasticity is a measure of how responsive the amount of labor workers are willing to offer (such as hours worked or participation) is to changes in wages or other economic incentives.
-
C.
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.
-
D.
economic policy
Economic policy is a set of government decisions and actions designed to influence a nation's economic performance, including growth, employment, inflation, and income distribution.
-
E.
housing policy experiment
A housing policy experiment is a structured, often time-bound initiative that tests specific housing interventions or regulations on a limited scale to evaluate their impacts on affordability, access, equity, and neighborhood outcomes before broader implementation.
- 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_69f224d9d52c8190a61f68ded37fa755 |
completed | April 29, 2026, 3:33 p.m. |
Created at: April 29, 2026, 9:10 p.m.