Triple

T26366170
Position Surface form Disambiguated ID Type / Status
Subject Brampton Battalion E660339 entity
Predicate ceasedPlayInBrampton P160459 FINISHED
Object 2013 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: 2013 | Statement: [Brampton Battalion, ceasedPlayInBrampton, 2013]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: ceasedPlayInBrampton
Context triple: [Brampton Battalion, ceasedPlayInBrampton, 2013]
  • A. retiredFromPlayingDueTo
    Indicates that an individual stopped actively participating in a sport or game because of the specified reason or cause.
  • B. laterPlayedFor
    Indicates that an individual was a member of or played for a team or organization at a time after a previously referenced team or organization.
  • C. disappearsFromPlayAfter
    Indicates that an entity is removed from active play and no longer participates in the game after a specified event or condition occurs.
  • D. associatedLostPlays
    Indicates a relationship where certain entities are linked to or connected with specific lost plays, typically as works that are missing, fragmentary, or no longer extant.
  • E. playedWithout
    Indicates that one participant engaged in a play-related activity while another expected or relevant participant was absent or not involved.
  • 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_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.
PDg Predicate description generation batch_69f6018ceb1c8190a6a5f84071659a96 completed May 2, 2026, 1:52 p.m.
Created at: April 26, 2026, 10:55 p.m.