Triple
T3147990
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | World Snooker Tour |
E65807
|
entity |
| Predicate | topPlayersCompete |
P18052
|
FINISHED |
| Object | top-ranked snooker players |
—
|
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: top-ranked snooker players | Statement: [World Snooker Tour, topPlayersCompete, top-ranked snooker players]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: topPlayersCompete Context triple: [World Snooker Tour, topPlayersCompete, top-ranked snooker players]
-
A.
featuresTopPlayersFrom
Indicates that something includes or showcases the most prominent or best-performing players from a specified source or group.
-
B.
competitionOf
Indicates a relationship where one entity is the competitive event, contest, or rivalry involving another entity.
-
C.
featuredCompetition
Indicates that a particular competition is highlighted or given special prominence relative to others.
-
D.
competitiveGame
Indicates a relationship where entities participate in a game or contest in which they compete against each other to win or achieve a higher ranking.
-
E.
featuresTopPlayers
chosen
Indicates that something prominently presents or showcases the most outstanding or highly ranked players.
- 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_69ad8584485081909ed529e890cadc4a |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada59a54188190a2e020fd4004d734 |
completed | March 8, 2026, 4:36 p.m. |
| PD | Predicate disambiguation | batch_69ad9dfa3d9081908425aa636bb9b897 |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:05 p.m.