Triple
T24608515
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hamilton Sports Group |
E609047
|
entity |
| Predicate | leagueAffiliationViaTeam |
P47876
|
FINISHED |
| Object | Canadian Premier League |
—
|
NE NERFINISHED |
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 Premier League | Statement: [Hamilton Sports Group, leagueAffiliationViaTeam, Canadian Premier League]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leagueAffiliationViaTeam Context triple: [Hamilton Sports Group, leagueAffiliationViaTeam, Canadian Premier League]
-
A.
leagueAffiliationThroughOwnedTeam
chosen
Indicates that an entity is affiliated with a league by virtue of owning a team that participates in that league.
-
B.
leagueAffiliationOfTeam
Indicates that a sports team is affiliated with, or competes within, a particular league.
-
C.
leagueAffiliationHistory
Indicates the historical sequence of leagues or organizations with which an entity has been affiliated over time.
-
D.
playerAffiliation
Indicates the organization, team, or group with which a player is formally associated or aligned.
-
E.
team2Affiliation
Indicates that an entity is affiliated with, belongs to, or is associated with a second team in a given context.
- 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_69e2c4d060e08190ac9f7c49b1036e20 |
completed | April 17, 2026, 11:40 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6ca751c8190a040c10d701ecf3a |
completed | April 30, 2026, 12:48 a.m. |
Created at: April 18, 2026, 2:31 a.m.