Triple
T7309660
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pakistan Super League |
E168058
|
entity |
| Predicate | formatOfCompetition |
P2673
|
FINISHED |
| Object | double round-robin |
—
|
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: double round-robin | Statement: [Pakistan Super League, formatOfCompetition, double round-robin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatOfCompetition Context triple: [Pakistan Super League, formatOfCompetition, double round-robin]
-
A.
competitionFormat
chosen
Indicates the specific structure or ruleset under which a competition is organized and conducted.
-
B.
typeOfCompetition
Indicates the specific kind or category of competition in which an entity participates or is involved.
-
C.
affectedCompetitionFormat
Indicates that one entity caused a change or influence on the structure, rules, or format of a competition.
-
D.
replacedCompetitionFormat
Indicates that one competition format was substituted for and took the place of another competition format.
-
E.
editionOfCompetition
Indicates that one entity is a specific edition or iteration of a recurring competition or tournament.
- 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_69c6888d8e3c81909db79714903baf31 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6ebdbd6f481908e69e53dab452656 |
completed | March 27, 2026, 8:43 p.m. |
| PD | Predicate disambiguation | batch_69c6e7705f4881909793071dee50c557 |
completed | March 27, 2026, 8:24 p.m. |
Created at: March 27, 2026, 3:01 p.m.