Triple
T4573950
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Africa national cricket team |
E123098
|
entity |
| Predicate | T20IDebutYear |
P26330
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [South Africa national cricket team, T20IDebutYear, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: T20IDebutYear Context triple: [South Africa national cricket team, T20IDebutYear, 2005]
-
A.
T20IDebutDate
Indicates the date on which an entity (typically a player or team) first appeared in a Twenty20 International (T20I) match.
-
B.
T20IDebutFor
Indicates that an entity made its Twenty20 International (T20I) debut while representing a specified team or side.
-
C.
T20IDebutAgainst
Indicates the opposing team against which a player made their Twenty20 International (T20I) debut.
-
D.
firstT20IYear
chosen
Indicates the year in which an entity (typically a player or team) first participated in a Twenty20 International (T20I) match.
-
E.
internationalDebutDateT20I
Indicates the date on which an entity (typically a player) first appeared in an international Twenty20 (T20I) match.
- 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_69bd46466c7081909d07f36be2d08804 |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd6632708c8190b627d99363ab062c |
completed | March 20, 2026, 3:22 p.m. |
| PD | Predicate disambiguation | batch_69bd620fc5e081908325ac8e6a6384ab |
completed | March 20, 2026, 3:04 p.m. |
Created at: March 20, 2026, 1:10 p.m.