Triple
T6103314
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohit Sharma |
E136056
|
entity |
| Predicate | hasScoredDoubleCenturyInODI |
P68151
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Rohit Sharma, hasScoredDoubleCenturyInODI, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasScoredDoubleCenturyInODI Context triple: [Rohit Sharma, hasScoredDoubleCenturyInODI, yes]
-
A.
highestOdiScore
Indicates that the subject has achieved the highest individual ODI (One Day International) cricket score among the compared entities.
-
B.
battedOver300Seasons
Indicates that a player achieved a batting average over .300 in one or more seasons.
-
C.
scoredFirstCenturyInIplHistory
Indicates that the subject is the player who achieved the first-ever century in the history of the Indian Premier League (IPL).
-
D.
leadingRunScorer
Indicates that the subject is the player who has scored the most runs (the top run-scorer) in a given match, series, tournament, or season.
-
E.
firstNewZealanderToScoreTestTripleCentury
Indicates that the subject is the first New Zealander ever to score 300 or more runs in a single Test cricket innings.
- 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_69c0087dee9881909e3655be88208c01 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c05b3dbc6c8190b9e3d81e6ca9eeb8 |
completed | March 22, 2026, 9:12 p.m. |
| PD | Predicate disambiguation | batch_69c049f5ac988190b62ba565153aaa35 |
completed | March 22, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69c04e8e3f2c8190be459ca02f9b315a |
completed | March 22, 2026, 8:18 p.m. |
Created at: March 22, 2026, 4:13 p.m.