Triple

T770461
Position Surface form Disambiguated ID Type / Status
Subject Rubinstein bargaining model E16268 entity
Predicate solutionConcept P4453 FINISHED
Object subgame perfect Nash equilibrium LITERAL FINISHED

How this triple was built (2 steps)

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.

NER Named-entity recognition gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: subgame perfect Nash equilibrium | Statement: [Rubinstein bargaining model, solutionConcept, subgame perfect Nash equilibrium]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: solutionConcept
Context triple: [Rubinstein bargaining model, solutionConcept, subgame perfect Nash equilibrium]
  • A. solutionType chosen
    Indicates the specific category or kind of solution associated with an entity or problem.
  • B. demonstratedConcept
    Indicates that an entity has shown, illustrated, or made evident a particular concept through example, explanation, or action.
  • C. isSolutionOf
    Indicates that one entity is a correct answer or satisfies the conditions of a given problem, equation, or task.
  • D. introducedConcept
    Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
  • E. challengedConcept
    Indicates that one entity has questioned, disputed, or called into doubt the validity, accuracy, or applicability of a particular concept.
  • F. None of above.

Provenance (3 batches)

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_69a49369a0848190af883934cee3db4c completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a704fb148190b203a5bdd77e961c completed March 1, 2026, 8:52 p.m.
PD Predicate disambiguation batch_69a4a508c42c8190850a0ac7844a3ea9 completed March 1, 2026, 8:43 p.m.
Created at: March 1, 2026, 7:37 p.m.