Triple
T18599074
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ricky Ponting |
E454570
|
entity |
| Predicate | retiredFromTestCricket |
P132728
|
FINISHED |
| Object | 2012 |
—
|
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: 2012 | Statement: [Ricky Ponting, retiredFromTestCricket, 2012]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromTestCricket Context triple: [Ricky Ponting, retiredFromTestCricket, 2012]
-
A.
retirementFromT20i
Indicates that an entity has formally retired from participating in Twenty20 International (T20I) cricket matches.
-
B.
hasPlayedDomesticCricketFor
Indicates that a person has been a member of and played domestic-level cricket matches for a specified team or organization.
-
C.
retiredAsPlayerFrom
Indicates that an individual ended their professional playing career while being associated with a specific team, organization, or context.
-
D.
retiredFromSidelines
Indicates that an entity has ended its role or involvement from a previously inactive, observing, or non-participatory position in a given context.
-
E.
steppedDownAsLimitedOversCaptain
Indicates that an entity resigned from the role of captain specifically for limited-overs formats of the sport.
- 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_69d8d38ae7e081908a98df1251842402 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5474f1d548190b74408eabd396344 |
completed | April 19, 2026, 9:21 p.m. |
| PD | Predicate disambiguation | batch_69e478cf5e888190a0b1074b0c6525df |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:45 a.m.