Triple
T25397403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wriddhiman Saha |
E636328
|
entity |
| Predicate | IPLFinalCenturyTeam |
P158262
|
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: [Wriddhiman Saha, IPLFinalCenturyTeam, Kings XI Punjab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IPLFinalCenturyTeam Context triple: [Wriddhiman Saha, IPLFinalCenturyTeam, Kings XI Punjab]
-
A.
IPLTeam
Indicates a relationship where an entity is recognized as a team that participates in the Indian Premier League (IPL) cricket competition.
-
B.
playedForIPLTeam
Indicates that one entity has been a player representing the specified IPL (Indian Premier League) team.
-
C.
traditionalCricketTeam
Indicates that an entity is a cricket team organized and composed according to customary or historically established rules and structures of the sport.
-
D.
ledTeamToIPLTitle
Indicates that a person, typically a captain or coach, successfully guided a cricket team to winning an Indian Premier League (IPL) championship.
-
E.
clubCricketTeam
Indicates that an entity is a cricket team that represents or is affiliated with a particular club.
- F. None of above. chosen
Provenance (4 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f584f5dda88190a24d7fb4ab0a45bd |
completed | May 2, 2026, 5 a.m. |
| PD | Predicate disambiguation | batch_69f45d0dbc8c8190beecce679fce90a4 |
completed | May 1, 2026, 7:58 a.m. |
| PDg | Predicate description generation | batch_69f464ae42e88190b3549fdf4e0b425e |
completed | May 1, 2026, 8:30 a.m. |
Created at: April 21, 2026, 1:50 p.m.