Triple
T3214627
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1992 World Series |
E67359
|
entity |
| Predicate | clinchingGameScore |
P36440
|
FINISHED |
| Object | Toronto Blue Jays 4–3 Atlanta Braves |
—
|
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: Toronto Blue Jays 4–3 Atlanta Braves | Statement: [1992 World Series, clinchingGameScore, Toronto Blue Jays 4–3 Atlanta Braves]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinchingGameScore Context triple: [1992 World Series, clinchingGameScore, Toronto Blue Jays 4–3 Atlanta Braves]
-
A.
clinchingGameState
Indicates a game state in which one side can secure a series, title, or advancement with a win (or, less commonly, face elimination with a loss).
-
B.
championshipGameScore
chosen
Indicates the final score achieved by each participant in a championship game.
-
C.
winningTeamScore
Indicates the number of points or goals achieved by the team that wins a particular game or competition.
-
D.
clinchingPlayDescription
Indicates the descriptive text of the specific play or action that secured a decisive victory or outcome in a game or competition.
-
E.
gameWinningScoreBy
Indicates that a particular score is the decisive amount by which a game is won by an 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_69ad858ac36c81909962589cd277d6e2 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adab085a408190af9fb40acca31a5f |
completed | March 8, 2026, 4:59 p.m. |
| PD | Predicate disambiguation | batch_69ad9e09b83881908801d79c3d9254f9 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:07 p.m.