Triple
T29413853
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colin Cowdrey |
E745969
|
entity |
| Predicate | halfCenturiesInTests |
P132592
|
FINISHED |
| Object | 38 |
—
|
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: 38 | Statement: [Colin Cowdrey, halfCenturiesInTests, 38]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: halfCenturiesInTests Context triple: [Colin Cowdrey, halfCenturiesInTests, 38]
-
A.
testHalfCenturies
chosen
Indicates the number or occurrence of half-century scores (50–99 runs) achieved, typically in a sporting or performance-testing context.
-
B.
odiHalfCenturies
Indicates the number of half-century (50–99 runs) scores a player has achieved in One Day International (ODI) cricket.
-
C.
numberOfODIDoubleCenturies
Indicates the count of double centuries a player has scored in One Day International (ODI) cricket matches.
-
D.
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.
-
E.
scoredCenturyIn
Indicates that a player scored 100 or more runs (a century) in a particular match, innings, or event.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a3b1e108190bec0049dc39f8926 |
completed | May 2, 2026, 9:18 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 2:59 p.m.