Triple
T13781602
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Snooker Championship |
E331143
|
entity |
| Predicate | finalMatchFormat |
P92809
|
FINISHED |
| Object | best of 35 frames |
—
|
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: best of 35 frames | Statement: [World Snooker Championship, finalMatchFormat, best of 35 frames]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalMatchFormat Context triple: [World Snooker Championship, finalMatchFormat, best of 35 frames]
-
A.
finalMatchType
Indicates the specific category or format of the concluding or decisive match in a series or competition.
-
B.
finalsSeriesFormat
chosen
Indicates the specific structure or rules governing how a finals series is organized and played (e.g., number of games, sequence, and format).
-
C.
finalMatches
Indicates that two or more items correspond exactly in their final or completed form, satisfying all criteria for being considered the same at the end state.
-
D.
finalMatchDecidedBy
Indicates that the outcome of a final match is determined by a specific method, event, or deciding factor.
-
E.
finalTournamentStage
Indicates that an event or match represents the concluding or championship stage of a tournament.
- 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_69d81c583b0081909e408a17db517a21 |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de02460a688190a27874f8d35819c7 |
completed | April 14, 2026, 9 a.m. |
| PD | Predicate disambiguation | batch_69dbbe98b5bc8190967907ec64d0317d |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 10:11 p.m.