Triple
T24029054
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2011 Indian Premier League |
E595043
|
entity |
| Predicate | eliminatorLoser |
P6984
|
FINISHED |
| Object | Mumbai Indians |
—
|
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: Mumbai Indians | Statement: [2011 Indian Premier League, eliminatorLoser, Mumbai Indians]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eliminatorLoser Context triple: [2011 Indian Premier League, eliminatorLoser, Mumbai Indians]
-
A.
loserElimination
chosen
Indicates that the entity identified as the loser in a competition, game, or contest is removed or disqualified from further participation.
-
B.
finalBoutLoser
Indicates that an entity is the competitor who lost in the final bout of a match, tournament, or competition.
-
C.
seedOfLoser
Indicates that one entity is the origin, cause, or initial source leading to another entity’s failure or loss.
-
D.
finalReplayLoser
Indicates that an entity is the participant who lost in the final replay (i.e., a rematch or replayed final) of a competition or contest.
-
E.
callsLosersBack
Indicates that an entity initiates a follow-up contact or response specifically to those entities that previously lost or were unsuccessful.
- 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.