Triple
T19700915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Final Stage |
E473091
|
entity |
| Predicate | isDecisiveRoundOf |
P125394
|
FINISHED |
| Object | Climax Series |
—
|
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: Climax Series | Statement: [Final Stage, isDecisiveRoundOf, Climax Series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isDecisiveRoundOf Context triple: [Final Stage, isDecisiveRoundOf, Climax Series]
-
A.
deciderInKnockout
chosen
Indicates that an entity serves as the deciding factor or tiebreaker in determining the outcome of a knockout-stage contest or match.
-
B.
finalMatchDetermines
Indicates that the outcome of a final match decides or establishes a particular result, status, or consequence for the related entities.
-
C.
finalMatchDecidedBy
Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
-
D.
wasSingleRound
Indicates that the related event or process consisted of only one round or iteration, without any repeats or additional rounds.
-
E.
decidedIn
Indicates that a decision, ruling, or outcome was made within a particular case, proceeding, or deliberative 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_69d8e515bef88190bc30781aea50537a |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e642b667908190841bb5fb7bfdb3f7 |
completed | April 20, 2026, 3:13 p.m. |
| PD | Predicate disambiguation | batch_69e530438c60819082364c7be3eef6f0 |
completed | April 19, 2026, 7:42 p.m. |
Created at: April 10, 2026, 1:46 p.m.