Triple
T24037293
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2023 Indian Premier League |
E595266
|
entity |
| Predicate | playoffMatches |
P8299
|
FINISHED |
| Object | Qualifier 1 |
—
|
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: Qualifier 1 | Statement: [2023 Indian Premier League, playoffMatches, Qualifier 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: playoffMatches Context triple: [2023 Indian Premier League, playoffMatches, Qualifier 1]
-
A.
playoffMeetingsEra
Indicates that two entities have faced each other in playoff competition during a specified historical era or time period.
-
B.
playoffRound
chosen
Indicates the specific stage or round within a playoff series in which a game, matchup, or event takes place.
-
C.
playoffsDetermine
Indicates that the outcome of playoff competitions decides or establishes a particular result, status, or ranking between the involved entities.
-
D.
playoffChampions
Indicates that the subject entity has won the playoff competition and is recognized as the overall champion for that playoff series or season.
-
E.
playoffMeetingsCount
Indicates the number of times the entities have faced each other in playoff competitions.
- 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_69f1d8d5fdc48190a037cf9447309356 |
completed | April 29, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69f1764345388190a3102b62ddb729b4 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 9:56 p.m.