Triple
T10990514
| 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 | instanceOf |
P0
|
FINISHED |
| Object | protocol |
C10322
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: protocol Context triple: [Additional Protocol to the Convention on Cybercrime, concerning the criminalisation of acts of a racist and xenophobic nature committed through computer systems, instanceOf, protocol]
-
A.
protocol service
A protocol service is a system component that implements, manages, and coordinates communication rules and message exchanges between distributed entities according to a defined protocol specification.
-
B.
communication protocol
A communication protocol is a defined set of rules and formats that enable reliable, structured exchange of data between two or more communicating entities in a networked system.
-
C.
protocol command
A protocol command is a structured instruction or message defined by a communication protocol that directs how participating systems should behave or exchange data.
-
D.
state protocol
chosen
A state protocol is a formal set of rules and procedures that governs how a state’s institutions, officials, and symbols interact internally and with other states to ensure order, recognition, and continuity.
-
E.
network protocol
A network protocol is a standardized set of rules and formats that enable computers and devices to communicate and exchange data reliably over a network.
- F. None of above.
Provenance (1 batch)
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. |
Created at: April 8, 2026, 9:24 p.m.