Triple
T33790998
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 4–3 Dodgers |
E865929
|
entity |
| Predicate | representsFinalScoreOf |
P2625
|
FINISHED |
| Object | Game 7 of the 2020 National League Championship Series |
—
|
NE NERFINISHED |
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 7 of the 2020 National League Championship Series | Statement: [4–3 Dodgers, representsFinalScoreOf, Game 7 of the 2020 National League Championship Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: representsFinalScoreOf Context triple: [4–3 Dodgers, representsFinalScoreOf, Game 7 of the 2020 National League Championship Series]
-
A.
finalScore
chosen
Indicates the resulting or overall score achieved after all contributing actions, events, or evaluations are completed.
-
B.
opponentFinalScore
Indicates the final score achieved by an opposing participant or team in a contest or game.
-
C.
finalSetScore
Indicates the final score achieved in a particular set within a match or game.
-
D.
finalReplayScore
Indicates the score or result achieved at the end of a replayed event, game, or scenario.
-
E.
finalScoreType
Indicates the specific category or type used to classify or interpret a final score in a given context.
- 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_69fefb15220081908da36aac386fa582 |
completed | May 9, 2026, 9:15 a.m. |
| PD | Predicate disambiguation | batch_69fefa8e8ad48190a723fed81e9d64d0 |
completed | May 9, 2026, 9:12 a.m. |
Created at: May 1, 2026, 1:45 a.m.