Triple
T33396541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kazakhstan Premier League clubs |
E855187
|
entity |
| Predicate | allowForeignPlayers |
P21278
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Kazakhstan Premier League clubs, allowForeignPlayers, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowForeignPlayers Context triple: [Kazakhstan Premier League clubs, allowForeignPlayers, yes]
-
A.
allowsForeignPlayers
chosen
Indicates that an entity permits participation or involvement by players who are from foreign countries or outside its primary jurisdiction.
-
B.
canLoanPlayersTo
Indicates that one entity has the authority or ability to temporarily transfer its players to another entity.
-
C.
allowsOveragePlayers
Indicates that a context, rule, or system permits participation or inclusion of players who exceed a specified age limit.
-
D.
usesDomesticPlayers
Indicates that an entity relies on or fields players who are from its own country or domestic system.
-
E.
professionalPlayersAllowedFrom
Indicates that professional players are permitted to participate starting from a specified point, such as a date, level, or stage.
- 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_69f3496e3f1c8190bcecfa82aa9d17ff |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fce7671f108190bf3ebf54339068b5 |
completed | May 7, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69fce5b5a84c81908ac1b5b9f08d48d0 |
completed | May 7, 2026, 7:19 p.m. |
Created at: May 1, 2026, 1:35 a.m.