Triple
T31868612
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Hawkins |
E813529
|
entity |
| Predicate | hasWorldChampionshipBestResult |
P45110
|
FINISHED |
| Object | runner-up |
—
|
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: runner-up | Statement: [Barry Hawkins, hasWorldChampionshipBestResult, runner-up]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasWorldChampionshipBestResult Context triple: [Barry Hawkins, hasWorldChampionshipBestResult, runner-up]
-
A.
WorldChampionshipBestResult
Indicates the best performance or highest placement an entity has ever achieved in a world championship competition.
-
B.
bestWorldChampionshipResult
chosen
Indicates the highest (best) world championship result or placement that an entity has achieved.
-
C.
hasBestGrandSlamResult
Indicates the relationship between an entity (e.g., a player) and the best performance or furthest round they have achieved in any Grand Slam tournament.
-
D.
driversChampionshipBestResult
Indicates the best finishing position a driver has ever achieved in a drivers’ championship.
-
E.
hasWorldChampionship
Indicates that an entity possesses, has won, or holds a world championship title or status.
- 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_69f348ecb07481909c8f72619131b115 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 30, 2026, 11:54 p.m.