Triple

T378511
Position Surface form Disambiguated ID Type / Status
Subject Western Conference E8622 entity
Predicate usesRegularSeasonStandingsFor P10473 FINISHED
Object playoff seeding 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: playoff seeding | Statement: [Western Conference, usesRegularSeasonStandingsFor, playoff seeding]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: usesRegularSeasonStandingsFor
Context triple: [Western Conference, usesRegularSeasonStandingsFor, playoff seeding]
  • A. includesPostseasonIn
    Indicates that a time period, schedule, or dataset explicitly encompasses postseason games or events in addition to the regular season.
  • B. regularSeasonWeeks
    Indicates the number of weeks that make up the regular season portion of a schedule or competition.
  • C. regularSeasonGamesPerTeam
    Indicates the number of games each team plays during the regular season.
  • D. hasAutomaticPlayoffBids
    Indicates that certain participants are guaranteed entry into a playoff competition without needing to qualify through regular selection or performance criteria.
  • E. usesPlayoffs
    Indicates that a competition or league determines its final standings or champion through a postseason playoff format rather than solely by regular-season results.
  • F. None of above. chosen

Provenance (4 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_69a2e7f47dd08190a4e294ccbbe46cd4 completed Feb. 28, 2026, 1:04 p.m.
NER Named-entity recognition batch_69a2ec2974988190a1d6316cbb5159c8 completed Feb. 28, 2026, 1:22 p.m.
PD Predicate disambiguation batch_69a2e96351cc8190a55adf95f8c27e9e completed Feb. 28, 2026, 1:10 p.m.
PDg Predicate description generation batch_69a2ea0be90881909e32d8fdb7aabb29 completed Feb. 28, 2026, 1:13 p.m.
Created at: Feb. 28, 2026, 1:08 p.m.