Triple
T22754337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anil Kumble |
E562796
|
entity |
| Predicate | TestWickets |
P57814
|
FINISHED |
| Object | over 600 wickets |
—
|
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: over 600 wickets | Statement: [Anil Kumble, TestWickets, over 600 wickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: TestWickets Context triple: [Anil Kumble, TestWickets, over 600 wickets]
-
A.
testWickets
chosen
Indicates the number of wickets a bowler takes (or is credited with) in a particular test cricket match or innings.
-
B.
tests
Indicates that one entity examines, evaluates, or checks another entity or condition to determine its properties, performance, or correctness.
-
C.
testSupport
Indicates that one entity provides assistance, resources, or infrastructure enabling another entity to perform or execute tests.
-
D.
leadingWicketTaker
Indicates that the subject holds the highest number of wickets taken in a given cricket competition, series, season, or context.
-
E.
test
Indicates that an entity performs, undergoes, or is associated with a testing or examination process involving another entity or condition.
- 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_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. |
Created at: April 17, 2026, 3:25 p.m.