Triple
T1328185
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Premier League |
E28377
|
entity |
| Predicate | isTopTierInSystem |
P7559
|
FINISHED |
| Object | 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: Canadian soccer league system | Statement: [Canadian Premier League, isTopTierInSystem, Canadian soccer league system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTopTierInSystem Context triple: [Canadian Premier League, isTopTierInSystem, Canadian soccer league system]
-
A.
playsInTopTier
Indicates that an entity participates as a competitor in the highest-level division or league within a given sport or competitive system.
-
B.
isTopLevelLeagueIn
chosen
Indicates that a sports league is the highest (top-tier) competitive level within a specified country or region.
-
C.
isToppedWith
Indicates that one entity serves as a topping placed on the surface of another entity.
-
D.
hasTopLevel
Indicates that one entity is the highest or primary element within a hierarchy or structure relative to another entity.
-
E.
isEntryLevelRankFor
Indicates that a rank represents the lowest or starting level within a particular role, position, or hierarchy.
- 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_69a498540a2481909e807a762280d3ba |
completed | March 1, 2026, 7:49 p.m. |
| NER | Named-entity recognition | batch_69a4c1c1d8188190b15a641a08345adc |
completed | March 1, 2026, 10:46 p.m. |
| PD | Predicate disambiguation | batch_69a4beef6a188190996f8775bdda8f6c |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:55 p.m.