Triple
T30500820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scarf’s lemma |
E776131
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | result in game theory |
C48681
|
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 game theory Context triple: [Scarf’s lemma, instanceOf, result in game theory]
-
A.
result in cooperative game theory
chosen
In cooperative game theory, a result is a formal theorem or proposition that characterizes properties of coalitions, solution concepts, or payoff allocations under specified assumptions about players’ cooperation and preferences.
-
B.
result in combinatorial game theory
In combinatorial game theory, a result is a formal outcome or conclusion—such as a theorem, lemma, or classification—that characterizes the behavior, value, or winning conditions of one or more games under specified rules.
-
C.
game-theoretic scenario
A game-theoretic scenario is a structured situation in which multiple decision-makers (players) with potentially conflicting interests choose strategies whose outcomes and payoffs depend on the combined actions of all participants.
-
D.
2×2 game
A 2×2 game is a strategic interaction between two players where each has two possible actions, producing four possible outcome combinations with associated payoffs.
-
E.
game theory literature
Game theory literature encompasses scholarly and applied works that develop, analyze, and apply mathematical models of strategic interaction among rational (or boundedly rational) decision-makers across economics, politics, biology, and related fields.
- 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.