Triple
T10990519
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Additional Protocol to the Convention on Cybercrime, concerning the criminalisation of acts of a racist and xenophobic nature committed through computer systems |
E259742
|
entity |
| Predicate | alsoKnownAs |
P39
|
FINISHED |
| Object | Protocol to the Convention on Cybercrime on the criminalisation of acts of a racist and xenophobic nature committed through computer systems |
E259742
|
NE 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: Protocol to the Convention on Cybercrime on the criminalisation of acts of a racist and xenophobic nature committed through computer systems | Statement: [Additional Protocol to the Convention on Cybercrime, concerning the criminalisation of acts of a racist and xenophobic nature committed through computer systems, alsoKnownAs, Protocol to the Convention on Cybercrime on the criminalisation of acts of a racist and xenophobic nature committed through computer systems]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Protocol to the Convention on Cybercrime on the criminalisation of acts of a racist and xenophobic nature committed through computer systems Context triple: [Additional Protocol to the Convention on Cybercrime, concerning the criminalisation of acts of a racist and xenophobic nature committed through computer systems, alsoKnownAs, Protocol to the Convention on Cybercrime on the criminalisation of acts of a racist and xenophobic nature committed through computer systems]
-
A.
Additional Protocol to the Convention on Cybercrime, concerning the criminalisation of acts of a racist and xenophobic nature committed through computer systems
chosen
The Additional Protocol to the Convention on Cybercrime is an international treaty that supplements the Budapest Convention by requiring states to criminalize online racist and xenophobic expression and improve cross-border cooperation in investigating such offences.
-
B.
Convention on Cybercrime
The Convention on Cybercrime is an international treaty that sets common standards for criminalizing and combating offenses committed via computer systems and the internet, and promotes cooperation among states in investigating and prosecuting such crimes.
-
C.
Second Additional Protocol to the Convention on Cybercrime on enhanced cooperation and disclosure of electronic evidence
The Second Additional Protocol to the Convention on Cybercrime is an international treaty instrument that strengthens cross-border cooperation and legal frameworks for obtaining and sharing electronic evidence in criminal investigations, particularly those involving cybercrime.
-
D.
Council of Europe Committee of Experts on Crime in Cyberspace
The Council of Europe Committee of Experts on Crime in Cyberspace was a specialized expert body within the Council of Europe responsible for developing international legal standards and policy guidance to combat cybercrime.
-
E.
Additional Protocol on Xenophobia and Racism
The Additional Protocol on Xenophobia and Racism is an international legal instrument to the Convention on Cybercrime that requires states to criminalize racist and xenophobic acts carried out via computer systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d6aa8a6a548190a750f944ccdc8064 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d787b8d7088190b7d6b63c3bac4ad1 |
completed | April 9, 2026, 11:04 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69e3a9644ff08190a3005e4f6a8243fe |
completed | April 18, 2026, 3:55 p.m. |
Created at: April 8, 2026, 9:24 p.m.