Triple
T37288849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Biogenesis scandal |
E925605
|
entity |
| Predicate | typeOfDoping |
P186765
|
FINISHED |
| Object | human growth hormone |
—
|
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: human growth hormone | Statement: [Biogenesis scandal, typeOfDoping, human growth hormone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfDoping Context triple: [Biogenesis scandal, typeOfDoping, human growth hormone]
-
A.
dopingCaseInvolvedSubstance
chosen
Indicates that a doping case involves or is associated with a particular prohibited substance.
-
B.
admittedToDoping
Indicates that an entity has confessed or acknowledged involvement in the use of prohibited performance-enhancing substances.
-
C.
canBeDopedWith
Indicates that one entity is capable of being modified or enhanced by introducing the other entity as a dopant.
-
D.
dopingProgram
Indicates a systematic plan or scheme in which performance-enhancing drugs are administered or used, typically to improve competitive outcomes.
-
E.
roleInDopingSystem
Indicates that an entity participates in a doping system with a specific function, responsibility, or level of involvement.
- 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_69f76eafe20c8190856d3b996a4c31a7 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a035ead9ee0819099806d2670dc9c50 |
completed | May 12, 2026, 5:09 p.m. |
| PD | Predicate disambiguation | batch_6a035dc9210c8190a9044c6a53211520 |
completed | May 12, 2026, 5:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.