Triple
T26283863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Umar Gul |
E661076
|
entity |
| Predicate | representedT20Franchise |
P65245
|
FINISHED |
| Object | Quetta Gladiators |
—
|
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: Quetta Gladiators | Statement: [Umar Gul, representedT20Franchise, Quetta Gladiators]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representedT20Franchise Context triple: [Umar Gul, representedT20Franchise, Quetta Gladiators]
-
A.
T20Franchise
chosen
Indicates that an entity is a professional cricket team participating in a Twenty20 (T20) franchise-based league.
-
B.
playedForIPLTeam
Indicates that one entity has been a player representing the specified IPL (Indian Premier League) team.
-
C.
IPLTeam
Indicates a relationship where an entity is recognized as a team that participates in the Indian Premier League (IPL) cricket competition.
-
D.
traditionalCricketTeam
Indicates that an entity is a cricket team organized and composed according to customary or historically established rules and structures of the sport.
-
E.
hasPlayedInT20League
Indicates that an entity (typically a player) has participated in at least one Twenty20 (T20) cricket league.
- 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_69ee812bbd448190be4d7478b057990a |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f71422adac8190a5ceb32dcf820833 |
completed | May 3, 2026, 9:23 a.m. |
| PD | Predicate disambiguation | batch_69f712764d2c819081b64b27e5de4a13 |
completed | May 3, 2026, 9:16 a.m. |
Created at: April 26, 2026, 10:02 p.m.