Triple

T26366191
Position Surface form Disambiguated ID Type / Status
Subject Brampton Battalion E660339 entity
Predicate bestPlayoffResult P22048 FINISHED
Object OHL conference championship finalist 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: OHL conference championship finalist | Statement: [Brampton Battalion, bestPlayoffResult, OHL conference championship finalist]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: bestPlayoffResult
Context triple: [Brampton Battalion, bestPlayoffResult, OHL conference championship finalist]
  • A. playoffResult
    Indicates the outcome of a playoff contest or series between competitors, such as who advanced or was eliminated.
  • B. playoffAchievement chosen
    Indicates that an entity has reached or accomplished a specific milestone or result in a playoff competition or postseason series.
  • C. playoffRecord
    Indicates the win-loss performance of an entity (such as a team or player) in postseason or playoff competitions.
  • D. wonPlayoffs
    Indicates that a team or player emerged as the overall victor in a playoff series or postseason competition.
  • E. previousPlayoffs
    Indicates that one entity participated in the playoffs that occurred immediately before the playoffs associated with the other entity.
  • 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_69ee8126d52c8190bc0b34337c2c9aa8 completed April 26, 2026, 9:18 p.m.
NER Named-entity recognition batch_69f6102c248c8190886da68d61d006dc completed May 2, 2026, 2:54 p.m.
PD Predicate disambiguation batch_69f5f800fa9c8190aab0962669fde8ac completed May 2, 2026, 1:11 p.m.
Created at: April 26, 2026, 10:55 p.m.