Triple
T18335915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorian Yates |
E439268
|
entity |
| Predicate | competitionWeightCategory |
P8068
|
FINISHED |
| Object | open bodybuilding |
—
|
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: open bodybuilding | Statement: [Dorian Yates, competitionWeightCategory, open bodybuilding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: competitionWeightCategory Context triple: [Dorian Yates, competitionWeightCategory, open bodybuilding]
-
A.
weightClass
chosen
Indicates the categorical grouping of an entity based on its weight range or mass classification.
-
B.
weightClassAlternativeName
Indicates that one weight class is referred to by an alternative name or label.
-
C.
competitionWeight
Indicates the weight or importance assigned to an entity within a competitive context or event.
-
D.
sportClassificationSystem
Indicates a system or scheme used to categorize and organize sports into defined types, groups, or classes based on shared characteristics or rules.
-
E.
competitionClass
Indicates that one entity is classified into a particular competitive category or level within a competition or contest.
- 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_69d8b9175fec8190af865699b4e64d8c |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e50ecd759481909703ed2d0d68199f |
completed | April 19, 2026, 5:20 p.m. |
| PD | Predicate disambiguation | batch_69e44fe91bc08190906518e1b120fcf0 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:37 a.m.