Triple
T19460235
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Game 7 of the 2016 World Series |
E486846
|
entity |
| Predicate | IndiansRunsScored |
P136006
|
FINISHED |
| Object | 7 |
—
|
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: 7 | Statement: [Game 7 of the 2016 World Series, IndiansRunsScored, 7]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: IndiansRunsScored Context triple: [Game 7 of the 2016 World Series, IndiansRunsScored, 7]
-
A.
topRunScorerRuns
Indicates the number of runs scored by the highest run-scorer in a given match, series, or tournament.
-
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.
firstClassRunsScored
Indicates the number of runs a player has scored in first-class cricket matches.
-
D.
highestOdiScore
Indicates that the subject has achieved the highest individual ODI (One Day International) cricket score among the compared entities.
-
E.
battedRunsScored
Indicates the number of runs a player scores as a direct result of their own batting actions.
- 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_69d8e8d86d608190bd199a98d0297f27 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e633c7f4388190be8c207c94ba8889 |
completed | April 20, 2026, 2:10 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7499a4819082bec0be8afba35c |
completed | April 19, 2026, 4:06 p.m. |
| PDg | Predicate description generation | batch_69e5004c23308190a087b7941a90725f |
completed | April 19, 2026, 4:18 p.m. |
Created at: April 10, 2026, 1:38 p.m.