Triple
T4516970
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hashim Amla |
E102174
|
entity |
| Predicate | highestTestScore |
P57161
|
FINISHED |
| Object | 311 not out |
—
|
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: 311 not out | Statement: [Hashim Amla, highestTestScore, 311 not out]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highestTestScore Context triple: [Hashim Amla, highestTestScore, 311 not out]
-
A.
highestPass
Indicates that an entity has achieved the greatest passing value, score, or level among a set of compared entities.
-
B.
highestPointsForm
Indicates that a given form or configuration achieves the greatest number of points compared to all other relevant forms.
-
C.
highestElement
Indicates that one element in a set or collection has a value greater than or equal to all other elements according to a specified ordering.
-
D.
highestRankIn
Indicates that one entity holds the top or most senior rank within a specified group, category, or context relative to other entities.
-
E.
hasMaximumGrade
Indicates that an entity possesses the highest possible grade or score within a defined grading or evaluation system.
- F. None of above. chosen
Provenance (4 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_69bd43d6251c81909deecce3e6e9d69c |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd572933408190b67c4ef6a7babe75 |
completed | March 20, 2026, 2:18 p.m. |
| PD | Predicate disambiguation | batch_69bd521abea48190b3e758a1f98dd55e |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd56b3e4c88190a7ade3d0ed0ab606 |
completed | March 20, 2026, 2:16 p.m. |
Created at: March 20, 2026, 1:02 p.m.