Triple
T22754343
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anil Kumble |
E562796
|
entity |
| Predicate | bowlingFigures |
P149607
|
FINISHED |
| Object | 10 for 74 in a Test innings |
—
|
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: 10 for 74 in a Test innings | Statement: [Anil Kumble, bowlingFigures, 10 for 74 in a Test innings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bowlingFigures Context triple: [Anil Kumble, bowlingFigures, 10 for 74 in a Test innings]
-
A.
bowlingSpecialty
Indicates that one entity has a particular area of skill or expertise in the sport of bowling with respect to another entity or context.
-
B.
bowlingStrength
Indicates the degree or effectiveness of one entity’s bowling performance or capability in relation to another.
-
C.
bowls
Indicates that an entity performs the action of bowling, typically rolling a ball toward a target such as pins or a wicket.
-
D.
associatedWithBowlingStyleOfPerson
Indicates a relationship where something is linked to or characterized by the specific bowling style used by a person.
-
E.
bowlingCoach
Indicates that one entity serves as a coach or instructor for another entity specifically in the sport of bowling.
- 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_69e24551ec7881909a9c924dbea155f6 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f179bb80ac8190b53a1e00704c4ff5 |
completed | April 29, 2026, 3:23 a.m. |
| PD | Predicate disambiguation | batch_69eed2b88d88819096015deb6a648801 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb5681f88190821129ced752f190 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:25 p.m.