Triple

T32657589
Position Surface form Disambiguated ID Type / Status
Subject Bulldogs E834902 entity
Predicate hasLevelInLeagueSystem P50168 FINISHED
Object major junior ice hockey 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: major junior ice hockey | Statement: [Bulldogs, hasLevelInLeagueSystem, major junior ice hockey]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasLevelInLeagueSystem
Context triple: [Bulldogs, hasLevelInLeagueSystem, major junior ice hockey]
  • A. hasTournamentLevel
    Indicates that an entity participates in or is classified by a specific competitive or organizational level within a tournament structure.
  • B. hasLevel
    Indicates that an entity possesses or is associated with a particular degree, rank, or stage within an ordered scale or hierarchy.
  • C. isTopLevelLeagueIn
    Indicates that a sports league is the highest (top-tier) competitive level within a specified country or region.
  • D. associatedLeagueLevel chosen
    Indicates that one entity is linked to another entity representing the competitive tier or level of a sports league.
  • E. supportsLeagueLevel
    Indicates that one entity provides the necessary conditions, resources, or authorization for a particular league level to exist or operate.
  • 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_69f3492f72248190ba42fa596aea50e1 completed April 30, 2026, 12:21 p.m.
NER Named-entity recognition batch_69fd7b0503a08190ba07338365b6fcc9 completed May 8, 2026, 5:56 a.m.
PD Predicate disambiguation batch_69fd7a9733dc81909199f453c0cc2bc1 completed May 8, 2026, 5:54 a.m.
Created at: May 1, 2026, 1:08 a.m.