Triple
T24029051
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Indian Premier League |
E595043
|
entity |
| Predicate | qualifier1Winner |
P127249
|
FINISHED |
| Object | Chennai Super Kings |
—
|
NE NERFINISHED |
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: Chennai Super Kings | Statement: [2011 Indian Premier League, qualifier1Winner, Chennai Super Kings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifier1Winner Context triple: [2011 Indian Premier League, qualifier1Winner, Chennai Super Kings]
-
A.
winnerQualifiedAs
Indicates that an entity became eligible or advanced to a particular status, role, or stage by virtue of having won a preceding contest or selection process.
-
B.
winnerQualifiedFrom
chosen
Indicates that an entity became a winner by advancing from a specified prior stage, event, or qualifying round.
-
C.
winnerFullName
Indicates the full personal name of the entity that is the winner in a given event or competition.
-
D.
winnerQualifiedFor
Indicates that the entity identified as the winner has earned or met the conditions required to qualify for a subsequent stage, event, or status.
-
E.
ownedWinnerOf
Indicates that an entity owns or possesses the winner of a specified competition, contest, or event.
- 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_69e288bf45f08190a1b6ed8cd0b9e86b |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1d76e10fc8190afa60c618a4398ee |
completed | April 29, 2026, 10:03 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:54 p.m.