Triple
T18569602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allan Border |
E453841
|
entity |
| Predicate | captaincyStartYearInODIs |
P115062
|
FINISHED |
| Object | 1985 |
—
|
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: 1985 | Statement: [Allan Border, captaincyStartYearInODIs, 1985]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: captaincyStartYearInODIs Context triple: [Allan Border, captaincyStartYearInODIs, 1985]
-
A.
captainODI
Indicates that the subject serves as the captain of the object’s team in One Day International (ODI) cricket matches.
-
B.
firstODIYear
Indicates the year in which an entity (typically a player or team) first participated in a One Day International (ODI) cricket match.
-
C.
internationalDebutDateODI
Indicates the date on which an entity (typically a player) first appeared in an international One Day International (ODI) match.
-
D.
servedAsCaptainFrom
chosen
Indicates that an entity held the role of captain of another entity starting from a specified point in time.
-
E.
internationalDebutOpponentODI
Indicates the opposing team against which a player made their One Day International (ODI) debut.
- 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_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. |
Created at: April 10, 2026, 11:43 a.m.