Triple
T32575832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Canadian Soccer League (post-2006) |
E832641
|
entity |
| Predicate | clubOwnershipModel |
P13376
|
FINISHED |
| Object | privately owned clubs |
—
|
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: privately owned clubs | Statement: [Canadian Soccer League (post-2006), clubOwnershipModel, privately owned clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubOwnershipModel Context triple: [Canadian Soccer League (post-2006), clubOwnershipModel, privately owned clubs]
-
A.
teamOwnershipModel
chosen
Indicates the type or structure of ownership relationship that exists between a team and its owning entity (such as an individual, group, or organization).
-
B.
teamOwner
Indicates that one entity holds ownership or controlling stake over a team.
-
C.
teamOwnershipRole
Indicates the specific ownership-related role or capacity an entity holds within a team (such as owner, co-owner, or managing owner).
-
D.
associatedClubOwner
Indicates that there is an ownership or proprietorship relationship between a club and its associated owner.
-
E.
teamOwnerFor
Indicates that one entity is the owner or controlling proprietor of a particular team.
- 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_69f349289adc81909f4374a58ec35a39 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c63e3ac081908cd2ee069e971cea |
completed | May 3, 2026, 3:51 a.m. |
| PD | Predicate disambiguation | batch_69f6bd2c138481908afa3ee3e91f8900 |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 1:04 a.m.