Triple
T1266622
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalai–Smorodinsky bargaining solution |
E15614
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | solution concept in cooperative game theory |
C3792
|
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: solution concept in cooperative game theory Context triple: [Kalai–Smorodinsky bargaining solution, instanceOf, solution concept in cooperative game theory]
-
A.
bargaining solution concept
chosen
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.
-
B.
work in social choice theory
Work in social choice theory examines how individual preferences can be aggregated into collective decisions, analyzing the fairness, consistency, and implications of different voting and choice mechanisms.
-
C.
infinite-horizon game
An infinite-horizon game is a strategic interaction that unfolds over an unbounded sequence of stages, where players’ decisions at each stage can affect payoffs and strategies indefinitely into the future.
-
D.
alternating-offers bargaining game
An alternating-offers bargaining game is a strategic interaction in which two or more parties sequentially propose and respond to offers over how to divide a surplus, with the possibility of delay affecting payoffs and outcomes.
-
E.
dynamic game
A dynamic game is a strategic interaction among multiple decision-makers that unfolds over time, where players’ choices at each stage can depend on past actions and information, influencing future payoffs and outcomes.
- 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_69a4935a94308190bb92555b79032824 |
completed | March 1, 2026, 7:28 p.m. |
Created at: March 1, 2026, 7:50 p.m.