Triple
T25293130
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Martin Guptill |
E634142
|
entity |
| Predicate | isAmongTopRunScorersIn |
P91094
|
FINISHED |
| Object | One Day Internationals globally |
—
|
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: One Day Internationals globally | Statement: [Martin Guptill, isAmongTopRunScorersIn, One Day Internationals globally]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAmongTopRunScorersIn Context triple: [Martin Guptill, isAmongTopRunScorersIn, One Day Internationals globally]
-
A.
isAmongTopScorers
chosen
Indicates that an entity ranks within the highest-performing group based on a scoring or evaluation metric.
-
B.
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.
-
C.
topRunScorerRuns
Indicates the number of runs scored by the highest run-scorer in a given match, series, or tournament.
-
D.
topScorer
Indicates that the subject is the individual with the highest score among a specified group or in a particular context.
-
E.
hasTopScorersList
Indicates that an entity maintains or is associated with a list of individuals or items ranked as top scorers.
- 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_69e75a9503d48190b80a005c6af0cb50 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48fcf4bc88190a9ffaa3b07d5b881 |
completed | May 1, 2026, 11:34 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 1:22 p.m.