Triple
T21740934
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Afghanistan national cricket team |
E536655
|
entity |
| Predicate | ICCAssociateMembershipYear |
P64978
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [Afghanistan national cricket team, ICCAssociateMembershipYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ICCAssociateMembershipYear Context triple: [Afghanistan national cricket team, ICCAssociateMembershipYear, 2013]
-
A.
NATOMembershipYear
Indicates the year in which an entity became a member of NATO.
-
B.
UNMembershipConsequenceYear
Indicates the year in which a specified consequence or outcome related to UN membership occurs or takes effect.
-
C.
ordinationYear
Indicates the year in which an individual was formally ordained to a religious office or role.
-
D.
joinedInYear
chosen
Indicates that an entity became a member of, or started participating in, another entity (such as an organization, group, or institution) in a specified calendar year.
-
E.
competitionYears
Indicates the years during which the entities were involved in a particular competition or competitive event.
- 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_69e0c46df5448190b4322127ffc4c690 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69f01a7250d48190aa63f89db017ef70 |
completed | April 28, 2026, 2:24 a.m. |
| PD | Predicate disambiguation | batch_69e6969c16fc8190b5126c169317d85d |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:49 p.m.