Triple
T19494520
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKCS #12 |
E487734
|
entity |
| Predicate | supportsIntegrityProtection |
P34886
|
FINISHED |
| Object | yes |
—
|
LITERAL 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: yes | Statement: [PKCS #12, supportsIntegrityProtection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsIntegrityProtection Context triple: [PKCS #12, supportsIntegrityProtection, yes]
-
A.
usesIntegrityCheck
Indicates that an entity employs a mechanism to verify the integrity or correctness of data, code, or operations.
-
B.
providesIntegrity
chosen
Indicates that one entity ensures the correctness, consistency, and protection from unauthorized alteration of another entity or its data.
-
C.
requiresMACForIntegrity
Indicates that the action or relationship is only considered to provide integrity if a Message Authentication Code (MAC) is used.
-
D.
supportsMemoryProtection
Indicates that one entity provides mechanisms to prevent unauthorized access or interference with another entity’s memory space.
-
E.
supportsReplayProtection
Indicates that the action or system includes mechanisms to prevent replaying previously valid messages or transactions as if they were new.
- F. None of above.
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_69d8e8d9d1c88190b01cd78b8be49384 |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e63490c16481908423e304d82722d7 |
completed | April 20, 2026, 2:13 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:40 p.m.