Triple
T31891762
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C.J. Hunter |
E814162
|
entity |
| Predicate | bannedForDoping |
P119097
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [C.J. Hunter, bannedForDoping, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bannedForDoping Context triple: [C.J. Hunter, bannedForDoping, yes]
-
A.
dopingBan
chosen
Indicates that an entity is prohibited from participating in a sport or competition due to violations of anti-doping rules.
-
B.
admittedToDoping
Indicates that an entity has confessed or acknowledged involvement in the use of prohibited performance-enhancing substances.
-
C.
notableDopingCase
Indicates that an entity is recognized for being involved in a significant or widely known doping (use of banned performance-enhancing substances) incident or scandal.
-
D.
dopingAdmissionYear
Indicates the year in which an entity admitted to involvement in doping.
-
E.
antiDopingControl
Indicates that an entity conducts, undergoes, or is associated with procedures to detect and prevent the use of prohibited performance-enhancing substances or methods.
- 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_69f348ef817481908440e2250319bcc8 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b158cc5c81909ce5b32c9a97ae72 |
completed | May 3, 2026, 2:22 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:58 p.m.