Triple
T31868611
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barry Hawkins |
E813529
|
entity |
| Predicate | madeMaximumBreakIn |
P172674
|
FINISHED |
| Object | professional competition |
—
|
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: professional competition | Statement: [Barry Hawkins, madeMaximumBreakIn, professional competition]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: madeMaximumBreakIn Context triple: [Barry Hawkins, madeMaximumBreakIn, professional competition]
-
A.
hasMaximumBreaks
Indicates that there is an upper limit on the number of breaks allowed or assigned in a given context.
-
B.
brokeRecordOf
Indicates that one entity has surpassed or exceeded a previous performance or achievement previously held by another entity.
-
C.
breaksBestIn
Indicates that one entity is most effective or optimal at breaking or penetrating another entity within a given context.
-
D.
brokeRecord
Indicates that one entity surpassed a previous best performance or achievement standard set by another (or itself) in a given domain.
-
E.
brokeSoundBarrier
Indicates that an entity achieved a speed exceeding the speed of sound, thereby breaking the sound barrier.
- F. None of above. chosen
Provenance (4 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_69f6b0959b948190881c0dfb16803a49 |
completed | May 3, 2026, 2:19 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
| PDg | Predicate description generation | batch_69f6af7d92008190aead47eaae8cc091 |
completed | May 3, 2026, 2:14 a.m. |
Created at: April 30, 2026, 11:54 p.m.