Triple
T4573722
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaminda Vaas |
E123093
|
entity |
| Predicate | retiredFromFormat |
P2644
|
FINISHED |
| Object | Test cricket |
—
|
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: Test cricket | Statement: [Chaminda Vaas, retiredFromFormat, Test cricket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: retiredFromFormat Context triple: [Chaminda Vaas, retiredFromFormat, Test cricket]
-
A.
retiredFrom
chosen
Indicates that an entity has permanently stopped working for or being active in a specified organization, role, or activity.
-
B.
retiredBy
Indicates that one entity has formally ended the active status, use, or service of another entity.
-
C.
retiredTo
Indicates that an entity has permanently left active service or work and taken up residence or status in a particular place or role as their retirement destination.
-
D.
returnedFromRetirement
Indicates that an entity has resumed an activity, role, or position after having previously retired from it.
-
E.
nameRetiredFrom
Indicates that an entity has ceased holding or performing a particular named role, position, or activity.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd58c89a5c81909a78bf0ac64777ad |
completed | March 20, 2026, 2:25 p.m. |
| PD | Predicate disambiguation | batch_69bd5227063c8190973155a875b013a7 |
completed | March 20, 2026, 1:56 p.m. |
Created at: March 20, 2026, 1:10 p.m.