Triple
T19494521
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PKCS #12 |
E487734
|
entity |
| Predicate | supportsPasswordProtection |
P15826
|
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, supportsPasswordProtection, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPasswordProtection Context triple: [PKCS #12, supportsPasswordProtection, yes]
-
A.
passwordProtectedBy
Indicates that access to an entity is restricted and can only be obtained by providing a specific password associated with another entity.
-
B.
protectionType
chosen
Indicates the kind or method of protection that is applied to or associated with an entity.
-
C.
hasProtectionPurpose
Indicates that something is intended or designed to serve a protective function or goal.
-
D.
protectionPolicy
Indicates that one entity establishes or enforces rules or measures to safeguard another entity from harm, loss, or risk.
-
E.
providesProtectionIn
Indicates that one entity offers protection or safeguarding to another entity within a specified context, location, or situation.
- 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.