Triple
T7365483
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Quetta Gladiators |
E169858
|
entity |
| Predicate | firstSeasonInPSL |
P26144
|
FINISHED |
| Object | 2016 |
—
|
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: 2016 | Statement: [Quetta Gladiators, firstSeasonInPSL, 2016]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSeasonInPSL Context triple: [Quetta Gladiators, firstSeasonInPSL, 2016]
-
A.
firstYearPlayed
chosen
Indicates the year in which an entity (such as a person or team) first began participating in the specified activity or domain.
-
B.
debutInLeague
Indicates the league in which an entity (typically a player or team) made its first official appearance.
-
C.
firstPlayed
Indicates that one entity was the earliest or initial thing (such as a song, game, or media item) that another entity engaged with or played.
-
D.
firstODIYear
Indicates the year in which an entity (typically a player or team) first participated in a One Day International (ODI) cricket match.
-
E.
firstT20IYear
Indicates the year in which an entity (typically a player or team) first participated in a Twenty20 International (T20I) match.
- 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_69c68a5ade988190885b7175f63b7534 |
completed | March 27, 2026, 1:47 p.m. |
| NER | Named-entity recognition | batch_69c6f26d6d6081909c7272a9ccae0d97 |
completed | March 27, 2026, 9:11 p.m. |
| PD | Predicate disambiguation | batch_69c6f02d36108190bcb34a95e6a30bd7 |
completed | March 27, 2026, 9:01 p.m. |
Created at: March 27, 2026, 3:06 p.m.