Triple
T16402711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Contributions to the Theory of Games |
E398339
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | game theory literature |
C37409
|
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: game theory literature Context triple: [Contributions to the Theory of Games, instanceOf, game theory literature]
-
A.
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.
-
B.
cooperative game
A cooperative game is a strategic situation in which players can form binding agreements and coalitions to share payoffs and work together to achieve mutually beneficial outcomes.
-
C.
bargaining solution concept
A bargaining solution concept is a formal rule or principle that specifies how two or more parties should divide the benefits of cooperation given their feasible payoffs and disagreement outcomes.
-
D.
combinatorial game
A combinatorial game is a two-player, perfect-information game with no chance elements where players move alternately and the outcome depends solely on their strategic choices under well-defined rules.
-
E.
theory of rational choice under risk
A theory of rational choice under risk explains how individuals should make decisions among uncertain outcomes by systematically comparing the expected utilities of available options, given their probabilities and the decision-maker’s preferences.
- F. None of above. chosen
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_69d87f2950248190bc8ad9b9bebdc8c8 |
completed | April 10, 2026, 4:40 a.m. |
Created at: April 10, 2026, 5:09 a.m.