Triple
T23924088
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Double |
E602296
|
entity |
| Predicate | clinchSeries |
P154382
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [The Double, clinchSeries, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: clinchSeries Context triple: [The Double, clinchSeries, true]
-
A.
championshipSeries
Indicates a competitive series of contests or games that determines a champion between qualifying participants.
-
B.
seriesClinchingShotBy
Indicates that a particular shot or play was made by an entity and directly resulted in clinching or deciding the outcome of a series.
-
C.
clinchingPlayDescription
Indicates the descriptive text of the specific play or action that secured a decisive victory or outcome in a game or competition.
-
D.
conferenceFinalsSeriesResult
Indicates the outcome of a conference finals playoff series between two competitors, including which side won and by what series score.
-
E.
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).
- 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_69e2953b928c819095395fa87baca583 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1cf1bdf108190b3c04146af8c3b3c |
completed | April 29, 2026, 9:27 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
| PDg | Predicate description generation | batch_69f16e348b548190b76e50f9b611f76d |
completed | April 29, 2026, 2:34 a.m. |
Created at: April 17, 2026, 8:42 p.m.