Triple
T28073615
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 Indian Premier League |
E709472
|
entity |
| Predicate | openingMatchAwayTeam |
P2621
|
FINISHED |
| Object | Kolkata Knight Riders |
—
|
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: Kolkata Knight Riders | Statement: [2008 Indian Premier League, openingMatchAwayTeam, Kolkata Knight Riders]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: openingMatchAwayTeam Context triple: [2008 Indian Premier League, openingMatchAwayTeam, Kolkata Knight Riders]
-
A.
awayTeam
chosen
Indicates that an entity is designated as the visiting or non-home team in a competitive event or match.
-
B.
coachAwayTeam
Indicates that a person serves as the coach of the away (visiting) team in a particular game or event.
-
C.
awayLeagueTeam
Indicates the team that is playing as the visiting (away) side in a league match.
-
D.
openingMatch
Indicates that one entity serves as the initial or first match, game, or contest in a series, event, or competition involving another entity.
-
E.
openingMatchResult
Indicates the outcome or result associated with the opening match in a series, tournament, or 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_69ef9b6f8078819098b741274cd1a2ee |
completed | April 27, 2026, 5:22 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 27, 2026, 8:47 p.m.