Triple
T24313917
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gale–Nikaidō–Debreu theorem |
E612750
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | theorem in mathematical economics |
C716
|
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: theorem in mathematical economics Context triple: [Gale–Nikaidō–Debreu theorem, instanceOf, theorem in mathematical economics]
-
A.
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.
-
B.
mathematical theorem
chosen
A mathematical theorem is a rigorously proven statement derived from axioms and previously established results, expressing a fundamental truth within a formal mathematical system.
-
C.
theorem in corporate finance
A theorem in corporate finance is a formally proven proposition that explains fundamental relationships among financial decisions, market conditions, and firm value within a rigorous mathematical or logical framework.
-
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 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.
- 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_69e2d7da491c8190b6e6218af50923db |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 18, 2026, 1:45 a.m.