Triple
T33791001
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4–3 Dodgers |
E865929
|
entity |
| Predicate | winningRuns |
P137384
|
FINISHED |
| Object | 4 |
—
|
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: 4 | Statement: [4–3 Dodgers, winningRuns, 4]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: winningRuns Context triple: [4–3 Dodgers, winningRuns, 4]
-
A.
mostRunsAward
Indicates that an entity has received an award for scoring the highest number of runs in a given competition or season.
-
B.
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.
-
C.
mostRuns
Indicates that one entity has scored a greater number of runs than all comparable entities in a given context or set.
-
D.
winningRunScorer
chosen
Indicates the player who scored the run that ultimately gave their team the decisive lead in the game.
-
E.
winsFor
Indicates that one entity achieves victory or success on behalf of, or in favor of, another entity.
- 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_69f3498f99f481909cb271f4965a7594 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 1:45 a.m.