Triple
T18569608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allan Border |
E453841
|
entity |
| Predicate | testStatusAtRetirement |
P132590
|
FINISHED |
| Object | most Test matches played |
—
|
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: most Test matches played | Statement: [Allan Border, testStatusAtRetirement, most Test matches played]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testStatusAtRetirement Context triple: [Allan Border, testStatusAtRetirement, most Test matches played]
-
A.
appliesToRetirementStatus
Indicates that the subject is relevant or applicable specifically to an entity’s retirement status or condition.
-
B.
hasRankAtRetirement
Indicates the rank or position an entity held at the time it retired or was formally withdrawn from active service.
-
C.
legalStatusAfterEndTime
Indicates the legal status or condition that applies to an entity after a specified end time has passed.
-
D.
hasLifetimeStatus
Indicates that an entity is associated with a status or condition that applies for the entire duration of its existence.
-
E.
hasSeniorityStatus
Indicates that one entity holds a particular level or classification of seniority relative to others.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b0075a08190a5d590d36089ca1e |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
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:43 a.m.