Triple

T38463876
Position Surface form Disambiguated ID Type / Status
Subject Vancouver Titans E912515 entity
Predicate expansionWave P193982 FINISHED
Object 2019 Overwatch League expansion 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: 2019 Overwatch League expansion | Statement: [Vancouver Titans, expansionWave, 2019 Overwatch League expansion]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: expansionWave
Context triple: [Vancouver Titans, expansionWave, 2019 Overwatch League expansion]
  • A. expansionUnit
    Indicates a unit or component that serves to extend, enlarge, or add capacity to another system, structure, or entity.
  • B. expansionPotential
    Indicates the capacity or likelihood for something to grow, extend, or increase beyond its current scope or state.
  • C. expansionSystem
    Indicates a relationship where a system undergoes or enables expansion, typically by increasing its scope, capacity, or components over time.
  • D. expansionOrContraction
    Indicates a change in size, volume, or extent of something, whether it is increasing (expanding) or decreasing (contracting).
  • E. expansionProject
    Indicates a project whose primary purpose is to enlarge, extend, or increase the capacity, scope, or reach of something.
  • 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_69f76e861d8c81908559031dc66e3c15 completed May 3, 2026, 3:49 p.m.
NER Named-entity recognition batch_69fd5bf69acc819092a01e4259785dc3 completed May 8, 2026, 3:43 a.m.
PD Predicate disambiguation batch_69fd59b3f4ac8190a7f9dd3142da6e09 completed May 8, 2026, 3:34 a.m.
PDg Predicate description generation batch_69fd5bf49288819098a12202411cba4f completed May 8, 2026, 3:43 a.m.
Created at: May 3, 2026, 4:31 p.m.