Triple
T3951562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2010 World Series |
E84875
|
entity |
| Predicate | clinchingScore |
P53087
|
FINISHED |
| Object | 3–1 |
—
|
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: 3–1 | Statement: [2010 World Series, clinchingScore, 3–1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinchingScore Context triple: [2010 World Series, clinchingScore, 3–1]
-
A.
clinchedBy
Indicates that a particular outcome, title, or achievement has been definitively secured or guaranteed by a specific entity.
-
B.
clinchingPlayDescription
Indicates the descriptive text of the specific play or action that secured a decisive victory or outcome in a game or competition.
-
C.
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).
-
D.
scoring
Indicates the act of achieving points or a measurable result, typically by successfully completing an action that contributes to a score or outcome.
-
E.
clinchingCity
Indicates the city in which a decisive or championship-clinching event, game, or outcome takes place.
- F. None of above. chosen
Provenance (4 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_69aed934fbfc8190847068e4546de963 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefaa5afdc8190b709af2473d75d02 |
completed | March 9, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69aef8ed04e4819096bced8971cd888d |
completed | March 9, 2026, 4:44 p.m. |
| PDg | Predicate description generation | batch_69aefaa3c6a08190bfe76629c7c98eea |
completed | March 9, 2026, 4:51 p.m. |
Created at: March 9, 2026, 3:30 p.m.