Triple
T12330285
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Joe Perry (snooker player) |
E293940
|
entity |
| Predicate | hasMaximumBreaks |
P104525
|
FINISHED |
| Object | 1 |
—
|
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: 1 | Statement: [Joe Perry (snooker player), hasMaximumBreaks, 1]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMaximumBreaks Context triple: [Joe Perry (snooker player), hasMaximumBreaks, 1]
-
A.
breaksBestOn
Indicates that something performs optimally or is most effective when it breaks or is broken under certain conditions or against certain targets.
-
B.
hasMaximumBreadth
Indicates that an entity possesses the greatest breadth (widest extent) among a set of comparable entities or within a defined context.
-
C.
breaksOn
Indicates that one entity fractures, shatters, or fails when subjected to contact with or force from another entity.
-
D.
isBreakoutSingleOf
Indicates that a single is recognized as the breakout or first major hit release for an artist or group.
-
E.
breaksBestIn
Indicates that one entity is most effective or optimal at breaking or penetrating another entity within a given context.
- 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_69d6ab6ae0dc8190b1522a9c1c55c114 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d93f634ee08190b4f533505d402219 |
completed | April 10, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69d93ec5be788190b82d2edc6a0f1095 |
completed | April 10, 2026, 6:17 p.m. |
| PDg | Predicate description generation | batch_69d93f607a88819089e89fd263ae9937 |
completed | April 10, 2026, 6:20 p.m. |
Created at: April 8, 2026, 9:53 p.m.