Triple
T22146753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zaheer Khan |
E547305
|
entity |
| Predicate | announcedInternationalRetirement |
P147162
|
FINISHED |
| Object | 2015 |
—
|
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: 2015 | Statement: [Zaheer Khan, announcedInternationalRetirement, 2015]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: announcedInternationalRetirement Context triple: [Zaheer Khan, announcedInternationalRetirement, 2015]
-
A.
announcedRetirementPlace
Indicates that an entity publicly declared their retirement while at or in a specific place.
-
B.
announcedRetirementFrom
Indicates that an entity has publicly declared its intention to retire from a particular role, position, organization, or activity.
-
C.
announcedRetirementBy
Indicates that one party has publicly declared the retirement of another party.
-
D.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
E.
announcedFor
Indicates that one entity has been publicly declared or made known in connection with, or on behalf of, another entity.
- 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_69e11e3a95d88190a3bd80d9471976c3 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f129f156988190bc9a24a37418e849 |
completed | April 28, 2026, 9:43 p.m. |
| PD | Predicate disambiguation | batch_69e71b384e008190b723c9a0f1089d66 |
completed | April 21, 2026, 6:37 a.m. |
| PDg | Predicate description generation | batch_69e7222d208c819098b12c13e31af629 |
completed | April 21, 2026, 7:07 a.m. |
Created at: April 16, 2026, 8:33 p.m.