Triple
T2001248
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Optional Protocol to the Convention against Torture |
E43475
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | optional protocol |
C10882
|
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: optional protocol Context triple: [Optional Protocol to the Convention against Torture, instanceOf, optional protocol]
-
A.
open standard
An open standard is a publicly available specification, developed and maintained through a transparent, collaborative process, that can be implemented and used by anyone without restrictive licensing.
-
B.
web protocol
A web protocol is a standardized set of rules and formats that govern how data is requested, transmitted, and received between clients and servers over the World Wide Web.
-
C.
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.
-
D.
cryptographic protocol
A cryptographic protocol is a precisely defined sequence of operations and message exchanges that uses cryptographic primitives to achieve security goals such as confidentiality, integrity, authentication, and non-repudiation between parties.
-
E.
official standard
An official standard is an authoritative, formally approved specification or guideline established by a recognized body to ensure consistency, compatibility, and quality across products, services, or processes.
- F. None of above. chosen
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_69a88715dbbc8190b2299e29e955d997 |
completed | March 4, 2026, 7:25 p.m. |
Created at: March 4, 2026, 7:37 p.m.