Triple
T25331162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohammad Shami |
E635154
|
entity |
| Predicate | formerIPLTeam |
P8967
|
FINISHED |
| Object | Kings XI Punjab |
—
|
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: Kings XI Punjab | Statement: [Mohammad Shami, formerIPLTeam, Kings XI Punjab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerIPLTeam Context triple: [Mohammad Shami, formerIPLTeam, Kings XI Punjab]
-
A.
playedForIPLTeam
Indicates that one entity has been a player representing the specified IPL (Indian Premier League) team.
-
B.
IPLTeam
Indicates a relationship where an entity is recognized as a team that participates in the Indian Premier League (IPL) cricket competition.
-
C.
IPLFinalCenturyTeam
Indicates that a team had a player score a century (100 or more runs) in the final match of an Indian Premier League (IPL) season.
-
D.
formerTeam2Name
Indicates that an entity was previously associated with a second former team identified by this name.
-
E.
formerSportsTeam
chosen
Indicates that an entity was once a member of or played for a particular sports team in the past but no longer does so.
- 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_69e75a9908108190a95427a97020632a |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f6b903538481909cffcb6cc1cc0e70 |
completed | May 3, 2026, 2:54 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
Created at: April 21, 2026, 1:30 p.m.