Triple
T17963512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Multan Sultans |
E449141
|
entity |
| Predicate | qualifiedForPlayoffs |
P28814
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Multan Sultans, qualifiedForPlayoffs, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: qualifiedForPlayoffs Context triple: [Multan Sultans, qualifiedForPlayoffs, 2020]
-
A.
wonPlayoffs
Indicates that a team or player emerged as the overall victor in a playoff series or postseason competition.
-
B.
usedForPlayoffQualification
Indicates that something serves as a basis or criterion for determining whether a team qualifies for the playoffs.
-
C.
hasPostseasonAccess
chosen
Indicates that an entity is granted the right or eligibility to participate in postseason or playoff competitions.
-
D.
usesPlayoffs
Indicates that a competition or league determines its final standings or champion through a postseason playoff format rather than solely by regular-season results.
-
E.
hasPlayoffsWith
Indicates that two entities participate together in the same playoff series, bracket, or postseason 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_69d8b9f9927c8190a006110c8b996e61 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e4b135cd2c8190a6190cf6611dbe08 |
completed | April 19, 2026, 10:40 a.m. |
| PD | Predicate disambiguation | batch_69e3f8fa62688190a5d5c361ab896256 |
completed | April 18, 2026, 9:34 p.m. |
Created at: April 10, 2026, 10:22 a.m.