Triple
T18569590
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allan Border |
E453841
|
entity |
| Predicate | numberOfODICenturies |
P23202
|
FINISHED |
| Object | 3 |
—
|
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: 3 | Statement: [Allan Border, numberOfODICenturies, 3]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfODICenturies Context triple: [Allan Border, numberOfODICenturies, 3]
-
A.
numberOfODIDoubleCenturies
Indicates the count of double centuries a player has scored in One Day International (ODI) cricket matches.
-
B.
odiCenturies
chosen
Indicates the number of centuries a player has scored in One Day International (ODI) cricket matches.
-
C.
testCenturies
Indicates that an entity has scored one or more centuries (100+ runs) in test cricket matches.
-
D.
completionCenturyGregorian
Indicates the century, in the Gregorian calendar system, during which the completion of something occurred.
-
E.
testDoubleCenturies
Indicates that an entity (typically a player) has achieved two or more scores of 200 or more runs in individual innings, usually within a specified context such as a series, career, or match format.
- 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.