Triple
T16559061
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Instituto dos Vinhos do Douro e do Porto |
E402288
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | certification authority |
C23785
|
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: certification authority Context triple: [Instituto dos Vinhos do Douro e do Porto, instanceOf, certification authority]
-
A.
certification body
chosen
A certification body is an independent organization that assesses and verifies whether products, services, systems, or individuals meet specified standards or requirements, and issues formal certificates to confirm compliance.
-
B.
registration authority
A registration authority is an entity responsible for verifying the identity and eligibility of subjects and approving or managing their registration within a specified system or domain.
-
C.
digital certificate
A digital certificate is an electronic credential issued by a trusted authority that binds a public key to an entity’s identity, enabling secure and authenticated communication over networks.
-
D.
public key infrastructure component
A public key infrastructure component is an element (such as a certificate authority, registration authority, or repository) that issues, manages, stores, and validates digital certificates and cryptographic keys to enable secure, trusted communications.
-
E.
interoperability certification
Interoperability certification is a formal validation process that confirms different systems, products, or services can reliably exchange and use information according to defined standards and protocols.
- 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_69d8838648088190acf97ef11fc3f61b |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:15 a.m.