Triple
T9671995
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jose Canseco |
E234050
|
entity |
| Predicate | accusedOthersOf |
P9856
|
FINISHED |
| Object | using performance-enhancing drugs |
—
|
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: using performance-enhancing drugs | Statement: [Jose Canseco, accusedOthersOf, using performance-enhancing drugs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: accusedOthersOf Context triple: [Jose Canseco, accusedOthersOf, using performance-enhancing drugs]
-
A.
accusedOf
chosen
Indicates that one entity has formally alleged or claimed that another entity committed a specific wrongdoing or offense.
-
B.
accusedIn
Indicates that a person or entity is formally charged with wrongdoing in a particular case, proceeding, or context.
-
C.
guiltyOf
Indicates that an entity has been judged or determined to have committed a particular offense, crime, or wrongful act.
-
D.
victimOfAccusation
Indicates that an entity is the target or subject of an accusation made by another party.
-
E.
wronglyAccusedBy
Indicates that one entity has falsely or unjustly accused another entity of wrongdoing.
- 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_69ca848f55e48190b3f67252571c3d45 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cd9c6aa01c819083fc758470096ec2 |
completed | April 1, 2026, 10:30 p.m. |
| PD | Predicate disambiguation | batch_69ccd5b5d40c8190850ad7a351445f32 |
completed | April 1, 2026, 8:22 a.m. |
Created at: March 30, 2026, 8:15 p.m.