Triple
T493245
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2008 World Series |
E10234
|
entity |
| Predicate | clinchingGame |
P7085
|
FINISHED |
| Object | Game 5 |
—
|
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: Game 5 | Statement: [2008 World Series, clinchingGame, Game 5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinchingGame Context triple: [2008 World Series, clinchingGame, Game 5]
-
A.
championshipGame
Indicates a game that determines the overall champion or winner of a competition or tournament.
-
B.
conferenceChampionshipGame
Indicates a game that determines the champion of a specific sports conference.
-
C.
seriesWinningGame
chosen
Indicates that a particular game is the decisive or clinching game in which one side wins the overall series.
-
D.
gameWinningKicker
Indicates that an entity serves as the kicker responsible for securing the decisive, game-winning score in a contest.
-
E.
tiebreaker
Indicates that one entity serves as the deciding factor used to break a tie between two or more otherwise equal options or outcomes.
- 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_69a2e847df8481909239ec08ccf1e376 |
completed | Feb. 28, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69a2f0faab4881909f65f172198b5bd2 |
completed | Feb. 28, 2026, 1:43 p.m. |
| PD | Predicate disambiguation | batch_69a2edf7ce008190836fb6ab5ea39375 |
completed | Feb. 28, 2026, 1:30 p.m. |
Created at: Feb. 28, 2026, 1:12 p.m.