Triple
T15436406
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sir Donald Bradman |
E369773
|
entity |
| Predicate | firstClassRunsScored |
P118777
|
FINISHED |
| Object | 28067 |
—
|
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: 28067 | Statement: [Sir Donald Bradman, firstClassRunsScored, 28067]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstClassRunsScored Context triple: [Sir Donald Bradman, firstClassRunsScored, 28067]
-
A.
leadingRunScorer
Indicates that the subject is the player who has scored the most runs (the top run-scorer) in a given match, series, tournament, or season.
-
B.
topRunScorerRuns
Indicates the number of runs scored by the highest run-scorer in a given match, series, or tournament.
-
C.
careerRunsScored
Indicates the total number of runs an entity has scored over the entire duration of their playing career.
-
D.
seriesWinningRunScoredBy
Indicates that a particular run, scored by a specific player, was the decisive run that clinched a series victory for that player’s team.
-
E.
battedRuns
Indicates that a player scored a specified number of runs while batting in a cricket (or similar bat-and-ball) context.
- 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_69d85a19180081909925012fbf4e62a3 |
completed | April 10, 2026, 2:02 a.m. |
| NER | Named-entity recognition | batch_69e03edb3ec481908b26164d4470c9bc |
completed | April 16, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69ded27f45548190a6d2b1b85cb47444 |
completed | April 14, 2026, 11:49 p.m. |
| PDg | Predicate description generation | batch_69ded57005608190886cd01f640dfedb |
completed | April 15, 2026, 12:01 a.m. |
Created at: April 10, 2026, 3:21 a.m.