Triple
T21726857
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kochi Tuskers Kerala |
E536295
|
entity |
| Predicate | statusInIPL |
P12781
|
FINISHED |
| Object | defunct franchise |
—
|
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: defunct franchise | Statement: [Kochi Tuskers Kerala, statusInIPL, defunct franchise]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: statusInIPL Context triple: [Kochi Tuskers Kerala, statusInIPL, defunct franchise]
-
A.
playedForIPLTeam
Indicates that one entity has been a player representing the specified IPL (Indian Premier League) team.
-
B.
IPLTeam
Indicates a relationship where an entity is recognized as a team that participates in the Indian Premier League (IPL) cricket competition.
-
C.
statusInLeague
chosen
Indicates the standing or rank an entity holds within a particular league or competitive organization.
-
D.
lostODIStatus
Indicates that an entity (typically a cricket team) has had its One Day International (ODI) status revoked or removed.
-
E.
homeStateTeamStatus
Indicates the status or condition of a team in relation to its designated home state.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd973ac648190bb09e20ac1be2d9b |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.