Triple
T19055190
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steve Smith |
E466374
|
entity |
| Predicate | testCenturiesCountOver |
P134919
|
FINISHED |
| Object | 30 |
—
|
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: 30 | Statement: [Steve Smith, testCenturiesCountOver, 30]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testCenturiesCountOver Context triple: [Steve Smith, testCenturiesCountOver, 30]
-
A.
testCenturies
Indicates that an entity has scored one or more centuries (100+ runs) in test cricket matches.
-
B.
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.
-
C.
testHalfCenturies
Indicates the number or occurrence of half-century scores (50–99 runs) achieved, typically in a sporting or performance-testing context.
-
D.
completionCenturyGregorian
Indicates the century, in the Gregorian calendar system, during which the completion of something occurred.
-
E.
testDebutCenturyOrFifty
Indicates that in a given test cricket debut match, the player scored either a century (100+ runs) or a fifty (50–99 runs).
- 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_69d8dd040fb881909af2a964f65ad208 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5dc056b708190a2b84cbddf0fc2d9 |
completed | April 20, 2026, 7:55 a.m. |
| PD | Predicate disambiguation | batch_69e4b99633c8819097988608c278ecf8 |
completed | April 19, 2026, 11:16 a.m. |
| PDg | Predicate description generation | batch_69e4c0fc3c4c8190abbfe06e1bd3325c |
completed | April 19, 2026, 11:48 a.m. |
Created at: April 10, 2026, 12:03 p.m.