Triple
T22229569
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jasprit Bumrah |
E549430
|
entity |
| Predicate | shirtNumberIPL |
P141214
|
FINISHED |
| Object | 93 |
—
|
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: 93 | Statement: [Jasprit Bumrah, shirtNumberIPL, 93]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shirtNumberIPL Context triple: [Jasprit Bumrah, shirtNumberIPL, 93]
-
A.
shirtNumberODI
Indicates the jersey number a player wears in One Day International (ODI) cricket matches.
-
B.
playedForIPLTeam
Indicates that one entity has been a player representing the specified IPL (Indian Premier League) team.
-
C.
shirtNumberTradition
Indicates a conventional or historically established assignment or significance of a particular shirt number within a team or sport.
-
D.
hasShirtNumberRole
chosen
Indicates that an entity holds a specific shirt number assignment or role, typically within a team or roster context.
-
E.
shirtNumberType
Indicates the type or category of a shirt number assigned to an entity (for example, a player’s jersey number type).
- 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_69e11e4102b881909cf47d3768e25c19 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f12bf173308190a3d21bfc59b39728 |
completed | April 28, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69e71b5177d881908f90abde14ada7dc |
completed | April 21, 2026, 6:38 a.m. |
Created at: April 16, 2026, 8:37 p.m.