Triple
T18739788
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Muttiah Muralitharan |
E458257
|
entity |
| Predicate | t20iRetirementYear |
P23206
|
FINISHED |
| Object | 2011 |
—
|
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: 2011 | Statement: [Muttiah Muralitharan, t20iRetirementYear, 2011]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: t20iRetirementYear Context triple: [Muttiah Muralitharan, t20iRetirementYear, 2011]
-
A.
t20iCaptaincyEndYear
Indicates the year in which an individual's tenure as captain in Twenty20 International (T20I) cricket came to an end.
-
B.
t20iCaptaincyStartYear
Indicates the year in which an entity first assumed the role of captain in Twenty20 International (T20I) cricket.
-
C.
retirementFromT20i
chosen
Indicates that an entity has formally retired from participating in Twenty20 International (T20I) cricket matches.
-
D.
t20IDebutYear
Indicates the year in which an entity (typically a player or team) made its debut in Twenty20 International (T20I) cricket.
-
E.
t20iCapNumber
Indicates that an entity has a specific cap number (e.g., a player’s official cap or appearance number) assigned to it.
- 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_69d8d394dc308190b6725073f5db324c |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e5768d6a208190817abe904fab433b |
completed | April 20, 2026, 12:42 a.m. |
| PD | Predicate disambiguation | batch_69e48d03766c8190a43f7681842f4f8d |
completed | April 19, 2026, 8:06 a.m. |
Created at: April 10, 2026, 11:51 a.m.