Triple
T30500821
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarf’s lemma |
E776131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in mathematical economics |
C55616
|
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: result in mathematical economics Context triple: [Scarf’s lemma, instanceOf, result in mathematical economics]
-
A.
result in econometrics
A result in econometrics is a formally derived conclusion—such as an estimate, test outcome, or theoretical proposition—about economic relationships based on statistical models and data.
-
B.
result in microeconomic theory
chosen
A result in microeconomic theory is a formally derived conclusion—often expressed as a theorem, proposition, or lemma—that characterizes how rational agents or markets behave under specified assumptions and institutional settings.
-
C.
economic theory
Economic theory is a conceptual framework that explains how individuals, firms, and governments make decisions about the allocation of scarce resources and how these decisions shape the production, distribution, and consumption of goods and services.
-
D.
economic equation
An economic equation is a mathematical expression that represents relationships between economic variables, such as supply and demand, costs and revenues, or income and expenditure, to analyze and predict economic behavior.
-
E.
result in mathematical physics
A result in mathematical physics is a rigorously proven statement that connects precise mathematical structures with physical theories, often clarifying, justifying, or predicting phenomena within a formal 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_69f22498c5d481908aaea89e6fab8280 |
completed | April 29, 2026, 3:32 p.m. |
Created at: April 29, 2026, 8:14 p.m.