Triple
T26837704
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROC |
E675681
|
entity |
| Predicate | relatedSanctionPeriod |
P125755
|
FINISHED |
| Object | WADA sanctions 2019–2022 |
—
|
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: WADA sanctions 2019–2022 | Statement: [ROC, relatedSanctionPeriod, WADA sanctions 2019–2022]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: relatedSanctionPeriod Context triple: [ROC, relatedSanctionPeriod, WADA sanctions 2019–2022]
-
A.
coSanctionedSince
Indicates that two or more entities have jointly imposed or been subject to a sanction starting from a specified point in time and continuing thereafter.
-
B.
relatedSanctions
chosen
Indicates that there is an association between an entity and one or more sanctions, such as penalties, restrictions, or punitive measures applied in connection with that entity.
-
C.
coSanctioningStartYear
Indicates the year in which a joint or collaborative sanctioning action officially began.
-
D.
coSanctionsWith
Indicates that two or more entities jointly impose, support, or participate in the same sanctions or sanctioning action.
-
E.
sanctionYear
Indicates the year in which a sanction was imposed, enacted, or came into effect.
- 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_69eee9b776448190993a60b67fcc9545 |
completed | April 27, 2026, 4:44 a.m. |
| NER | Named-entity recognition | batch_69fef5cf8da881908260ec633830375d |
completed | May 9, 2026, 8:52 a.m. |
| PD | Predicate disambiguation | batch_69fef455e40481909861c82007b79bc0 |
completed | May 9, 2026, 8:46 a.m. |
Created at: April 27, 2026, 5:05 a.m.