Triple
T793512
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ITU Telecommunication Standardization Sector |
E16966
|
entity |
| Predicate | notableStandard |
P321
|
FINISHED |
| Object | X.509 |
E6784
|
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: X.509 | Statement: [ITU Telecommunication Standardization Sector, notableStandard, X.509]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: X.509 Context triple: [ITU Telecommunication Standardization Sector, notableStandard, X.509]
-
A.
X.509 certificates
chosen
X.509 certificates are digital documents that bind a public key to an entity’s identity using a trusted certificate authority, forming the basis of public key infrastructure for secure communications.
-
B.
PKCS #1
PKCS #1 is a cryptographic standard that defines the mathematical properties, formats, and padding schemes for implementing RSA encryption and digital signatures.
-
C.
S/MIME
S/MIME is a widely used standard for secure email that provides encryption and digital signatures using public key cryptography.
-
D.
ASN.1
ASN.1 (Abstract Syntax Notation One) is a standardized, platform-independent notation used to define and encode complex data structures in telecommunications and cryptographic protocols, including X.509 certificates.
-
E.
RFC 2818
RFC 2818 is the Internet standard that specifies how HTTP is used over TLS/SSL, defining the HTTPS protocol and its security requirements.
- 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_69a4936cb7448190914f5fe4b8d81607 |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a79a3bbc81908d818c50a366b0f8 |
completed | March 1, 2026, 8:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69a678828f848190bbd511eb277db4ef |
completed | March 3, 2026, 5:58 a.m. |
Created at: March 1, 2026, 7:38 p.m.