Triple
T36271240
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nepal national cricket team |
E892678
|
entity |
| Predicate | ODIStatusReconfirmedYear |
P149409
|
FINISHED |
| Object | 2023 |
—
|
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: 2023 | Statement: [Nepal national cricket team, ODIStatusReconfirmedYear, 2023]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ODIStatusReconfirmedYear Context triple: [Nepal national cricket team, ODIStatusReconfirmedYear, 2023]
-
A.
ODIStatus
Indicates that an entity’s status or condition is classified according to One Day International (ODI) criteria, typically in the context of cricket matches or teams.
-
B.
confirmationYear
Indicates the calendar year in which a confirmation event or formal validation of something took place.
-
C.
reaffirmationYear
chosen
Indicates the year in which a previously established agreement, decision, or commitment is formally confirmed or renewed.
-
D.
ICCStatusYear
Indicates the year in which an entity’s status with the International Cricket Council (ICC) is recorded or applies.
-
E.
authorizationYear
Indicates the year in which an official approval, permission, or authorization for something was granted.
- 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_69f7c29e1b848190b945c6c6120a5330 |
completed | May 3, 2026, 9:48 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b6e7a881908deb96bedb2713f4 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:09 p.m.