Triple
T15234373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunrisers Hyderabad |
E364085
|
entity |
| Predicate | firstIPLSeason |
P117674
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Sunrisers Hyderabad, firstIPLSeason, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstIPLSeason Context triple: [Sunrisers Hyderabad, firstIPLSeason, 2013]
-
A.
firstODIYear
Indicates the year in which an entity (typically a player or team) first participated in a One Day International (ODI) cricket match.
-
B.
firstT20IYear
Indicates the year in which an entity (typically a player or team) first participated in a Twenty20 International (T20I) match.
-
C.
firstOdiTournament
Indicates that the subject entity is the first ODI (One Day International) cricket tournament in which the object entity participated or was involved.
-
D.
firstT20IDate
Indicates the date on which an entity (such as a player or team) first participated in a Twenty20 International (T20I) match.
-
E.
firstPremierLeagueSeason
Indicates the specific Premier League season in which an entity (typically a club or player) first participated.
- F. None of above. chosen
Provenance (4 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_69d85a0ce24c81909c4d3b6475548c95 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e007d7237081908dc17900ee66b64f |
completed | April 15, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69deca899d5c8190be4a7c71e1683c69 |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:12 a.m.