Triple
T33396498
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Football Federation of Kazakhstan |
E855186
|
entity |
| Predicate | leftAsianFootballConfederation |
P36481
|
FINISHED |
| Object | 2001 |
—
|
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: 2001 | Statement: [Football Federation of Kazakhstan, leftAsianFootballConfederation, 2001]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: leftAsianFootballConfederation Context triple: [Football Federation of Kazakhstan, leftAsianFootballConfederation, 2001]
-
A.
asiaCupWinner
Indicates that one entity is the champion or winning team of the Asia Cup tournament in a given edition or year.
-
B.
AsianChampionshipTitles
Indicates the number of championship titles an entity has won in Asian-level competitions or tournaments.
-
C.
conferenceAFC
chosen
Indicates that an entity is affiliated with or participates in the AFC (Asian Football Confederation) conference.
-
D.
wonAsianCupWinnersCup
Indicates that one entity (typically a sports team or club) has won the Asian Cup Winners' Cup competition.
-
E.
hasFootballAssociation
Indicates that there exists an affiliation or formal relationship between an entity and a football (soccer) association or governing body.
- 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_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:35 a.m.