Triple

T801778
Position Surface form Disambiguated ID Type / Status
Subject NHL Metropolitan Division E17142 entity
Predicate wildCardEligibility P84 FINISHED
Object eligible for Eastern Conference wild-card spots 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: eligible for Eastern Conference wild-card spots | Statement: [NHL Metropolitan Division, wildCardEligibility, eligible for Eastern Conference wild-card spots]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: wildCardEligibility
Context triple: [NHL Metropolitan Division, wildCardEligibility, eligible for Eastern Conference wild-card spots]
  • A. eligibility chosen
    Indicates that an entity meets the required conditions or qualifications to participate in, receive, or perform something.
  • B. wildCardBerth
    Indicates that an entity receives a berth or qualification through a wildcard allocation rather than through standard qualification criteria.
  • C. eligibilityUnit
    Indicates that one entity serves as the unit or basis used to determine another entity’s eligibility for a benefit, status, or condition.
  • D. eligibilityLevel
    Indicates the degree or tier of qualification an entity has for a given benefit, service, or status.
  • E. formerEligibilityRule
    Indicates that an entity was previously subject to a particular eligibility rule, but that rule no longer currently applies.
  • 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_69a49378b9c48190adbf5f62e5b7aca1 completed March 1, 2026, 7:28 p.m.
NER Named-entity recognition batch_69a4a7cd6b98819080898934552a72f9 completed March 1, 2026, 8:55 p.m.
PD Predicate disambiguation batch_69a4a5133bf88190a613e96d1f7cffa7 completed March 1, 2026, 8:44 p.m.
Created at: March 1, 2026, 7:38 p.m.