Triple
T21726931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wasim Akram |
E536297
|
entity |
| Predicate | isFirstToReach |
P21887
|
FINISHED |
| Object | 500 ODI wickets |
—
|
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: 500 ODI wickets | Statement: [Wasim Akram, isFirstToReach, 500 ODI wickets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isFirstToReach Context triple: [Wasim Akram, isFirstToReach, 500 ODI wickets]
-
A.
firstToAchieve
chosen
Indicates that one entity was the earliest or initial entity to accomplish or attain a specified goal, status, or outcome before any others.
-
B.
tieForFirstPlace
Indicates that two or more competitors share the highest rank or score, resulting in no single clear winner.
-
C.
firstWinner
Indicates that the subject is the entity who achieved first place or victory in the referenced event or competition.
-
D.
firstRunningWinner
Indicates that the subject is the first entity to win among those participating in a running event or race.
-
E.
stageReachedByWinner
Indicates the competition stage that the eventual winner had reached or achieved.
- 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_69e0c46d3284819099a4f9d5a704eb95 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69efd973ac648190bb09e20ac1be2d9b |
completed | April 27, 2026, 9:47 p.m. |
| PD | Predicate disambiguation | batch_69e6969725bc81908e7ad19619ba2688 |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:48 p.m.