Triple
T22443578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ravindra Jadeja |
E554813
|
entity |
| Predicate | formerIplTeam |
P133375
|
FINISHED |
| Object | Rajasthan Royals |
—
|
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: Rajasthan Royals | Statement: [Ravindra Jadeja, formerIplTeam, Rajasthan Royals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerIplTeam Context triple: [Ravindra Jadeja, formerIplTeam, Rajasthan Royals]
-
A.
playedForIPLTeam
chosen
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.
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.
team2FormerName
Indicates that the second team entity was previously known by a different name.
- 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_69e11e5010e48190ae1e9c9db9697637 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15ae40f9081908674015beb33f74e |
completed | April 29, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69e898a327948190beee5e168006a0a7 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:47 p.m.