Triple
T34779755
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Steele (cricketer) |
E1002611
|
entity |
| Predicate | testDebutSeries |
P57171
|
FINISHED |
| Object | Ashes series |
—
|
NE NERFINISHED |
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: Ashes series | Statement: [David Steele (cricketer), testDebutSeries, Ashes series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: testDebutSeries Context triple: [David Steele (cricketer), testDebutSeries, Ashes series]
-
A.
testDebut
Indicates the event or context in which an entity (such as a product, feature, or work) is first introduced or used in a testing environment.
-
B.
testDebutFor
chosen
Indicates that an entity makes its first appearance or performance in a particular test event, context, or setting.
-
C.
launchesSeries
Indicates that one entity initiates or starts a sequence or series of related events, actions, or items involving another entity.
-
D.
testSeriesOf
Indicates that one entity is a test or evaluation designed to be applied sequentially or collectively to a series of related entities.
-
E.
seriesRunStart
Indicates the point in time or event at which a particular series or sequence of related items begins.
- 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_69f76db30a108190bb57ca95b873e5bb |
completed | May 3, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f77ffa6b68819090257fed3802c239 |
completed | May 3, 2026, 5:03 p.m. |
| PD | Predicate disambiguation | batch_69f7795978c481909e152cd1bd02dd07 |
completed | May 3, 2026, 4:35 p.m. |
Created at: May 3, 2026, 3:59 p.m.