Triple
T18569593
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allan Border |
E453841
|
entity |
| Predicate | odiHighestScore |
P132586
|
FINISHED |
| Object | 127* |
—
|
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: 127* | Statement: [Allan Border, odiHighestScore, 127*]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: odiHighestScore Context triple: [Allan Border, odiHighestScore, 127*]
-
A.
highestODIScoreOpponent
Indicates the opposing team or player against whom an entity has achieved its highest individual ODI (One Day International) score.
-
B.
eloHighestRanking
Indicates that one entity holds the highest Elo rating or ranking within a specified group or context relative to other entities.
-
C.
highestTestScoreOpponent
Indicates that the related entity is the opponent who achieved the highest test score among all considered opponents.
-
D.
recordHighScoringForWinner
Indicates that a record is kept of the highest score achieved by the winning entity in a given context or event.
-
E.
hasHighest
Indicates that one entity possesses the greatest value, rank, or level in a specified attribute or set compared to all others.
- 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_69d8d38974308190a9174430ef256b73 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e53b0075a08190a5d590d36089ca1e |
completed | April 19, 2026, 8:28 p.m. |
| PD | Predicate disambiguation | batch_69e478c16e0c8190b03966aa23c395a6 |
completed | April 19, 2026, 6:40 a.m. |
| PDg | Predicate description generation | batch_69e484121cd48190bf583b4c94636a30 |
completed | April 19, 2026, 7:28 a.m. |
Created at: April 10, 2026, 11:43 a.m.