Triple
T5737702
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Little Master |
E126538
|
entity |
| Predicate | associatedWithBattingStyleOfPerson |
P65538
|
FINISHED |
| Object | right-handed batsman |
—
|
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: right-handed batsman | Statement: [Little Master, associatedWithBattingStyleOfPerson, right-handed batsman]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedWithBattingStyleOfPerson Context triple: [Little Master, associatedWithBattingStyleOfPerson, right-handed batsman]
-
A.
battingStrength
Indicates the relative power or effectiveness of an entity’s batting performance in a given context.
-
B.
ESPNcricinfoPlayerId
Indicates that there is an association between a person (typically a cricketer) and their unique player identifier used on the ESPNcricinfo website.
-
C.
CricbuzzPlayerId
Indicates a relationship where a player is associated with their unique identifier on the Cricbuzz platform.
-
D.
battingPowerplayHistory
Indicates the historical record of batting performances specifically during powerplay overs in past matches or innings.
-
E.
battingPosition
Indicates the specific order or spot in which a player appears in a batting lineup or batting order.
- 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_69c0083082288190b7478cead6b5430a |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c0255c8c308190821f968ec41c5078 |
completed | March 22, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69c021c8195481909419808b002628aa |
completed | March 22, 2026, 5:07 p.m. |
| PDg | Predicate description generation | batch_69c022a50c048190aff24c63e7039dd6 |
completed | March 22, 2026, 5:11 p.m. |
Created at: March 22, 2026, 3:47 p.m.