Triple
T25397383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wriddhiman Saha |
E636328
|
entity |
| Predicate | formatPlayedForIndia |
P2170
|
FINISHED |
| Object | Test cricket |
—
|
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: Test cricket | Statement: [Wriddhiman Saha, formatPlayedForIndia, Test cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formatPlayedForIndia Context triple: [Wriddhiman Saha, formatPlayedForIndia, Test cricket]
-
A.
debutForIndiaFormat
Indicates the event or context in which an individual made their first official appearance for India in a specific cricket format.
-
B.
notableBatsmanForIndia
Indicates that a person is recognized as a notable batsman who has played cricket for the Indian national team.
-
C.
playedFor
chosen
Indicates that one entity has been a member of or participated as a player for a particular team, organization, or group.
-
D.
playedInCricketWorldCup
Indicates that an entity has participated as a player in at least one Cricket World Cup tournament.
-
E.
lastOverBowlerForIndia
Indicates that the referenced player was the most recent bowler to deliver an over for the India cricket team in that match or innings.
- 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_69e75db263888190b77fff9e2827b9a2 |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f61f12b0f08190bc4a16907941864c |
completed | May 2, 2026, 3:58 p.m. |
| PD | Predicate disambiguation | batch_69f61b37a5648190b10d33ae205ccfee |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 21, 2026, 1:50 p.m.