Triple
T13976779
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Indian Premier League |
E336206
|
entity |
| Predicate | ChennaiSuperKingsTitles |
P30586
|
FINISHED |
| Object | 5 |
—
|
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: 5 | Statement: [Indian Premier League, ChennaiSuperKingsTitles, 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ChennaiSuperKingsTitles Context triple: [Indian Premier League, ChennaiSuperKingsTitles, 5]
-
A.
ledTeamToIPLTitle
Indicates that a person, typically a captain or coach, successfully guided a cricket team to winning an Indian Premier League (IPL) championship.
-
B.
IPLTeam
Indicates a relationship where an entity is recognized as a team that participates in the Indian Premier League (IPL) cricket competition.
-
C.
hasTeamsChampionship
Indicates that an entity has won at least one championship title in a teams-based competition or league.
-
D.
T20Franchise
Indicates that an entity is a professional cricket team participating in a Twenty20 (T20) franchise-based league.
-
E.
teamWonChampionship
chosen
Indicates that a particular team has secured victory in a championship competition.
- 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_69d81c639e808190a0e4b4f3d31c6a59 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de2e90dc148190b38e339aac0de484 |
completed | April 14, 2026, 12:09 p.m. |
| PD | Predicate disambiguation | batch_69dd465a21408190b912a42c50ffa0d9 |
completed | April 13, 2026, 7:39 p.m. |
Created at: April 9, 2026, 10:18 p.m.