Triple
T7805274
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Imran Khan |
E180532
|
entity |
| Predicate | retirementFromInternationalCricketYear |
P37546
|
FINISHED |
| Object | 1992 |
—
|
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: 1992 | Statement: [Imran Khan, retirementFromInternationalCricketYear, 1992]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retirementFromInternationalCricketYear Context triple: [Imran Khan, retirementFromInternationalCricketYear, 1992]
-
A.
retirementFromT20i
Indicates that an entity has formally retired from participating in Twenty20 International (T20I) cricket matches.
-
B.
endOfInternationalCareer
chosen
Indicates that an entity’s participation or involvement in international-level activities or competitions has concluded.
-
C.
internationalDebutDateODI
Indicates the date on which an entity (typically a player) first appeared in an international One Day International (ODI) match.
-
D.
retirementYearAsPlayer
Indicates the year in which an individual ended their career as an active player.
-
E.
hasPlayedDomesticCricketFor
Indicates that a person has been a member of and played domestic-level cricket matches for a specified team or organization.
- 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_69ca827e50cc8190a92a733577184938 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69caf78a6d88819093f83528fe88b182 |
completed | March 30, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69cae9111b2481909684a2d4aa4831c2 |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 4:35 p.m.