Triple
T31868604
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Hawkins |
E813529
|
entity |
| Predicate | hasRankingTitle |
P90523
|
FINISHED |
| Object | Australian Goldfields Open |
—
|
NE NERFINISHED |
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: Australian Goldfields Open | Statement: [Barry Hawkins, hasRankingTitle, Australian Goldfields Open]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRankingTitle Context triple: [Barry Hawkins, hasRankingTitle, Australian Goldfields Open]
-
A.
hasRankingCategory
Indicates that an entity is associated with a particular ranking category or tier within an ordered classification system.
-
B.
hasRankOrTitle
chosen
Indicates that an entity holds, is assigned, or is associated with a specific rank, title, or formal designation.
-
C.
hasRankingUnit
Indicates that one entity is associated with a specific unit or scale used to express its ranking or ordered position.
-
D.
hasRankingPoints
Indicates that an entity possesses a certain number of ranking points used to determine its position or standing within a ranking system.
-
E.
useRankTitles
Indicates that rank-based titles are applied or displayed for the entities involved.
- 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_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 30, 2026, 11:54 p.m.