Triple
T23312653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KMIP |
E590624
|
entity |
| Predicate | governingBody |
P46
|
FINISHED |
| Object | OASIS KMIP Technical Committee |
—
|
NE NERFINISHED |
How this triple was built (3 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: OASIS KMIP Technical Committee | Statement: [KMIP, governingBody, OASIS KMIP Technical Committee]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: OASIS KMIP Technical Committee Context triple: [KMIP, governingBody, OASIS KMIP Technical Committee]
-
A.
KMIP
KMIP (Key Management Interoperability Protocol) is an industry-standard protocol that enables interoperable communication and management of cryptographic keys and related security objects across diverse systems and devices.
-
B.
OASIS Security Services Technical Committee
The OASIS Security Services Technical Committee is a working group within the OASIS standards organization responsible for developing and maintaining security-related specifications for web services and identity management.
-
C.
OASIS DITA Technical Committee
The OASIS DITA Technical Committee is the standards body within OASIS responsible for developing and maintaining the DITA XML-based architecture for structured, topic-oriented content.
-
D.
IETF JOSE Working Group
The IETF JOSE Working Group is an Internet Engineering Task Force group responsible for developing standards for JSON-based object signing and encryption used in web security protocols.
-
E.
NIST SP 800-56C
NIST SP 800-56C is a NIST Special Publication that provides recommendations for key derivation methods in key-establishment schemes used in cryptographic systems.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: OASIS KMIP Technical Committee Target entity description: The OASIS KMIP Technical Committee is the standards body within OASIS responsible for developing and maintaining the Key Management Interoperability Protocol (KMIP) specifications and related guidance.
-
A.
KMIP
KMIP (Key Management Interoperability Protocol) is an industry-standard protocol that enables interoperable communication and management of cryptographic keys and related security objects across diverse systems and devices.
-
B.
OASIS Security Services Technical Committee
The OASIS Security Services Technical Committee is a working group within the OASIS standards organization responsible for developing and maintaining security-related specifications for web services and identity management.
-
C.
OASIS DITA Technical Committee
The OASIS DITA Technical Committee is the standards body within OASIS responsible for developing and maintaining the DITA XML-based architecture for structured, topic-oriented content.
-
D.
IETF JOSE Working Group
The IETF JOSE Working Group is an Internet Engineering Task Force group responsible for developing standards for JSON-based object signing and encryption used in web security protocols.
-
E.
NIST SP 800-56C
NIST SP 800-56C is a NIST Special Publication that provides recommendations for key derivation methods in key-establishment schemes used in cryptographic systems.
- F. None of above. chosen
Provenance (2 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_69e25d1d32188190948eb76909d1dcc3 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1972ca70481909e2415c65964210a |
completed | April 29, 2026, 5:29 a.m. |
Created at: April 17, 2026, 5:06 p.m.