Triple
T13781666
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK Championship |
E331144
|
entity |
| Predicate | prizeFund |
P15222
|
FINISHED |
| Object | one of the highest in snooker |
—
|
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: one of the highest in snooker | Statement: [UK Championship, prizeFund, one of the highest in snooker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: prizeFund Context triple: [UK Championship, prizeFund, one of the highest in snooker]
-
A.
prizeFundType
Indicates the type or category of a prize fund associated with an award, competition, or financial pool.
-
B.
prizeContext
Indicates the situational or contextual circumstances under which a prize is awarded, considered, or relevant.
-
C.
prizePool
chosen
Indicates that a certain amount of rewards or funds is collectively available to be distributed among participants in an event, competition, or activity.
-
D.
prizeType
Indicates the specific category or kind of prize associated with an entity or event.
-
E.
awardAmount
Indicates the specific quantity or value of an award that is granted in the context of a particular awarding event or relationship.
- 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_69dbc85fb600819098a2aab48169be96 |
completed | April 12, 2026, 4:29 p.m. |
Created at: April 9, 2026, 10:11 p.m.