Triple
T6103316
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rohit Sharma |
E136056
|
entity |
| Predicate | highestODIScore |
P64583
|
FINISHED |
| Object | 264 |
—
|
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: 264 | Statement: [Rohit Sharma, highestODIScore, 264]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestODIScore Context triple: [Rohit Sharma, highestODIScore, 264]
-
A.
highestOdiScore
chosen
Indicates that the subject has achieved the highest individual ODI (One Day International) cricket score among the compared entities.
-
B.
highestTestScore
Indicates that one entity has achieved the greatest test score among a specified set or in a given context.
-
C.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
-
D.
highestTestScoreOpponent
Indicates that the related entity is the opponent who achieved the highest test score among all considered opponents.
-
E.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
- 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_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. |
Created at: March 22, 2026, 4:13 p.m.