Triple

T131719
Position Surface form Disambiguated ID Type / Status
Subject Nash bargaining solution E2666 entity
Predicate solutionForm P3660 FINISHED
Object argmax of (u1 - d1)(u2 - d2) over feasible set 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: argmax of (u1 - d1)(u2 - d2) over feasible set | Statement: [Nash bargaining solution, solutionForm, argmax of (u1 - d1)(u2 - d2) over feasible set]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: solutionForm
Context triple: [Nash bargaining solution, solutionForm, argmax of (u1 - d1)(u2 - d2) over feasible set]
  • A. solutionType
    Indicates the specific category or kind of solution associated with an entity or problem.
  • B. admitsSolution
    Indicates that a problem, system, or situation allows for or possesses at least one valid solution.
  • C. hasFormulation chosen
    Indicates that one entity is expressed, prepared, or configured in a particular form or composition defined by another entity.
  • D. support
    Indicates that one entity provides assistance, endorsement, or backing to another entity or its actions.
  • E. dissolved
    Indicates that one substance has been mixed into another so thoroughly that it forms a uniform solution and is no longer distinguishable as a separate phase.
  • 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_69a2520c0f3481908b0ed054a2fca8d0 completed Feb. 28, 2026, 2:25 a.m.
NER Named-entity recognition batch_69a25855baf48190a1b63f2e5865d957 completed Feb. 28, 2026, 2:52 a.m.
PD Predicate disambiguation batch_69a2564edb488190974dc00eb9ac37d9 completed Feb. 28, 2026, 2:43 a.m.
Created at: Feb. 28, 2026, 2:30 a.m.