Triple
T4573948
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Africa national cricket team |
E123098
|
entity |
| Predicate | ODIDebutYear |
P7549
|
FINISHED |
| Object | 1991 |
—
|
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: 1991 | Statement: [South Africa national cricket team, ODIDebutYear, 1991]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ODIDebutYear Context triple: [South Africa national cricket team, ODIDebutYear, 1991]
-
A.
ODIDebutDate
Indicates the date on which an entity (typically a player or team) first appeared in a One Day International (ODI) cricket match.
-
B.
teamStartYear
Indicates the year in which an entity (such as a person or organization) began its association with a particular team.
-
C.
managerDebutYear
Indicates the year in which an individual first began their role as a manager.
-
D.
debutYear
chosen
Indicates the year in which an entity first appeared, was introduced, or made its initial public debut.
-
E.
ODIDebutFor
Indicates that an entity made its official debut appearance or performance for a particular team or organization in a One Day International (ODI) 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.