Triple
T27743019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | K3 League |
E701902
|
entity |
| Predicate | clubOwnershipTypes |
P13376
|
FINISHED |
| Object | corporate-backed 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: corporate-backed clubs | Statement: [K3 League, clubOwnershipTypes, corporate-backed clubs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clubOwnershipTypes Context triple: [K3 League, clubOwnershipTypes, corporate-backed 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.
teamOwnershipRole
Indicates the specific ownership-related role or capacity an entity holds within a team (such as owner, co-owner, or managing owner).
-
C.
associatedClubOwner
Indicates that there is an ownership or proprietorship relationship between a club and its associated owner.
-
D.
sportOwnershipArea
Indicates the geographic area or region over which a particular sport organization, team, or entity holds ownership or control rights.
-
E.
teamOwner
Indicates that one entity holds ownership or controlling stake over a 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_69ef6a53c7388190899baa6daf42301c |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63894e5848190aec428392562ab06 |
completed | May 2, 2026, 5:47 p.m. |
| PD | Predicate disambiguation | batch_69f6370c8c7c8190a02ea82847bb6e76 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 4:13 p.m.