Triple
T26837688
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ROC |
E675681
|
entity |
| Predicate | sanctioningOrganizations |
P96540
|
FINISHED |
| Object | World 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: World Anti-Doping Agency | Statement: [ROC, sanctioningOrganizations, World Anti-Doping Agency]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sanctioningOrganizations Context triple: [ROC, sanctioningOrganizations, World Anti-Doping Agency]
-
A.
sanctioningOrganization
chosen
Indicates the organization that formally imposes, authorizes, or enforces a sanction on another party.
-
B.
bannedOrganizations
Indicates that certain organizations are officially prohibited or outlawed, typically by a governing authority or policy.
-
C.
organizationTypeOfSanctioningBody
Indicates the type or category of organization that serves as the sanctioning body in a given context.
-
D.
laterSanctioningBody
Indicates that one entity serves as a subsequent or replacement sanctioning authority for another entity or event.
-
E.
contributingOrganization
Indicates an organization that plays a role in creating, supporting, or otherwise contributing to the production or provision of something.
- 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_69f61fd623bc819091df736cf3419b99 |
completed | May 2, 2026, 4:01 p.m. |
| PD | Predicate disambiguation | batch_69f61b3d23f481908dfec27adace900a |
completed | May 2, 2026, 3:41 p.m. |
Created at: April 27, 2026, 5:05 a.m.