Triple
T36271236
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepal national cricket team |
E892678
|
entity |
| Predicate | T20IStatusFromYear |
P132619
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Nepal national cricket team, T20IStatusFromYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: T20IStatusFromYear Context triple: [Nepal national cricket team, T20IStatusFromYear, 2014]
-
A.
lastT20IYear
Indicates the year in which an entity (typically a player or team) most recently participated in a Twenty20 International (T20I) match.
-
B.
T20IDebutDate
Indicates the date on which an entity (typically a player or team) first appeared in a Twenty20 International (T20I) match.
-
C.
t20IDebutYear
chosen
Indicates the year in which an entity (typically a player or team) made its debut in Twenty20 International (T20I) cricket.
-
D.
t20iCaptaincyEndYear
Indicates the year in which an individual's tenure as captain in Twenty20 International (T20I) cricket came to an end.
-
E.
T20WorldCupAppearances
Indicates the number of times an entity has participated in T20 Cricket World Cup tournaments.
- 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_69f76e488f34819083e254dbe288c27a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7be9d07ac8190adf796cbef60daf6 |
completed | May 3, 2026, 9:31 p.m. |
| PD | Predicate disambiguation | batch_69f7bcccd7988190aa5c931ff347d33c |
completed | May 3, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:09 p.m.