Triple
T23912538
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alberto Salazar |
E601981
|
entity |
| Predicate | sanctionImposedBy |
P122155
|
FINISHED |
| Object | United States Anti-Doping Agency |
—
|
NE NERFINISHED |
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: United States Anti-Doping Agency | Statement: [Alberto Salazar, sanctionImposedBy, United States Anti-Doping Agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctionImposedBy Context triple: [Alberto Salazar, sanctionImposedBy, United States Anti-Doping Agency]
-
A.
imposesSanctionsOn
chosen
Indicates that one entity enforces punitive or restrictive measures against another entity, typically to influence or penalize its behavior.
-
B.
typeOfSanctionsAuthority
Indicates the authority or legal basis under which specific sanctions are imposed or administered.
-
C.
coSanctionedBy
Indicates that an action, decision, or measure is jointly authorized, approved, or endorsed by multiple entities.
-
D.
sanctionsTarget
Indicates that an entity imposes sanctions or punitive measures against another entity as its target.
-
E.
laterSanctioningBody
Indicates that one entity serves as a subsequent or replacement sanctioning authority for another entity or event.
- 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_69e2953a187081908346a9f36e85fc98 |
completed | April 17, 2026, 8:16 p.m. |
| NER | Named-entity recognition | batch_69f1ce95f4848190b98339d8a6c988ba |
completed | April 29, 2026, 9:25 a.m. |
| PD | Predicate disambiguation | batch_69f16151ebdc819086e9e1d7cc1f4f3c |
completed | April 29, 2026, 1:39 a.m. |
Created at: April 17, 2026, 8:39 p.m.