Triple

T6995441
Position Surface form Disambiguated ID Type / Status
Subject Vancouver FC E162200 entity
Predicate domesticCompetitionLevel P18266 FINISHED
Object top tier of Canadian soccer league system 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: top tier of Canadian soccer league system | Statement: [Vancouver FC, domesticCompetitionLevel, top tier of Canadian soccer league system]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: domesticCompetitionLevel
Context triple: [Vancouver FC, domesticCompetitionLevel, top tier of Canadian soccer league system]
  • A. primaryCompetitionLevel chosen
    Indicates the main or highest level of competition at which an entity primarily competes or operates.
  • B. domesticCupLevel
    Indicates the competitive tier or stage of a team’s participation within a domestic cup competition.
  • C. levelOfCompetition
    Indicates the intensity or degree of competitive pressure present in a given context or interaction.
  • D. competitionLevel
    Indicates the degree or intensity of competitive pressure or rivalry present in a given context or interaction.
  • E. featuredCompetitionLevel
    Indicates that a particular competition level is highlighted or given special prominence relative to other levels.
  • 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_69c68857ffc08190857dc62cd5253777 completed March 27, 2026, 1:38 p.m.
NER Named-entity recognition batch_69c6dbec259c8190bb4cfbc1ff6fc786 completed March 27, 2026, 7:35 p.m.
PD Predicate disambiguation batch_69c6d7c4a18881908d267137daed828b completed March 27, 2026, 7:17 p.m.
Created at: March 27, 2026, 2:32 p.m.