Triple
T4016882
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | David Ross |
E90782
|
entity |
| Predicate | scoredInGame |
P31381
|
FINISHED |
| Object | 2016 World Series Game 7 home run |
—
|
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: 2016 World Series Game 7 home run | Statement: [David Ross, scoredInGame, 2016 World Series Game 7 home run]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scoredInGame Context triple: [David Ross, scoredInGame, 2016 World Series Game 7 home run]
-
A.
scoredInMatch
chosen
Indicates that an entity (typically a player or team) scored during a particular match.
-
B.
scoredFor
Indicates that one entity achieved points or a score on behalf of another entity, such as a player scoring for a team.
-
C.
hasScoredFor
Indicates that one entity has scored points, goals, or similar achievements on behalf of another entity, such as a team, organization, or side.
-
D.
pointsScored
Indicates the number of points an entity has earned or achieved in a particular event, game, or context.
-
E.
scoredInTournament
Indicates that an entity achieved a score or points during a particular tournament.
- 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_69aed95e44088190aff7d90a151b1b20 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaec08dc8190a341809059554f84 |
completed | March 9, 2026, 4:53 p.m. |
| PD | Predicate disambiguation | batch_69aef8fa6fec81909b1190ecbba61410 |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:35 p.m.