Triple
T7223467
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Protocol No. 1 to the European Convention on Human Rights |
E150318
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | additional protocol |
C21515
|
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: additional protocol Context triple: [Protocol No. 1 to the European Convention on Human Rights, instanceOf, additional protocol]
-
A.
optional protocol
An optional protocol is a set of behaviors or methods that a class or object may implement but is not required to, allowing flexible and partial conformance to a shared interface.
-
B.
state protocol
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.
-
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.
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.
-
E.
cryptographic protocol message
A cryptographic protocol message is a structured unit of data exchanged between parties in a cryptographic protocol, containing information such as identifiers, nonces, keys, and signatures to achieve security goals like confidentiality, integrity, and authentication.
- 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_69c687effb44819092b95d07d0368c9f |
completed | March 27, 2026, 1:36 p.m. |
Created at: March 27, 2026, 2:54 p.m.