Triple

T22742112
Position Surface form Disambiguated ID Type / Status
Subject 1979 NHL–WHA merger E562439 entity
Predicate includedIndemnityPayments P144330 FINISHED
Object true 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: true | Statement: [1979 NHL–WHA merger, includedIndemnityPayments, true]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: includedIndemnityPayments
Context triple: [1979 NHL–WHA merger, includedIndemnityPayments, true]
  • A. includesPayment chosen
    Indicates that one entity contains, involves, or provides a monetary payment as part of its terms, contents, or execution.
  • B. hasIndemnity
    Indicates that one party provides indemnification or protection to another party against specified losses, damages, or liabilities.
  • C. indemnityBasis
    Indicates that one party’s obligation to compensate another for loss, damage, or liability is determined according to a specified indemnification standard or method.
  • D. indemnityPayableOverYears
    Indicates that an indemnity obligation is to be paid out in installments over a specified number of years rather than as a single lump sum.
  • E. requiredIndemnityReceiver
    Indicates that one party is obligated to provide indemnity (compensation or protection against loss) to another specified party.
  • 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_69e245513a5c81908d5cb471b4fc429d completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f1797400fc8190bec26726f434f787 completed April 29, 2026, 3:22 a.m.
PD Predicate disambiguation batch_69eed2a971c0819088af574e40c9343f completed April 27, 2026, 3:06 a.m.
Created at: April 17, 2026, 3:23 p.m.