Triple
T22109360
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NIPRNET |
E546373
|
entity |
| Predicate | hasUserAuthentication |
P38481
|
FINISHED |
| Object | Public Key Infrastructure certificates |
—
|
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: Public Key Infrastructure certificates | Statement: [NIPRNET, hasUserAuthentication, Public Key Infrastructure certificates]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasUserAuthentication Context triple: [NIPRNET, hasUserAuthentication, Public Key Infrastructure certificates]
-
A.
hasUser
Indicates that an entity is associated with or linked to a specific user.
-
B.
hasCredential
chosen
Indicates that an entity possesses or has been granted a specific credential, qualification, or certification.
-
C.
hasUserService
Indicates that an entity is associated with or utilizes a particular user-related service.
-
D.
hasHumanAccess
Indicates that a human is able to access, use, or interact with the referenced entity or resource.
-
E.
authenticationRequired
Indicates that access to a resource or operation is restricted and can only be performed by entities that have successfully authenticated.
- 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_69e11e378dc08190896d6a51597afd5a |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f1291b9c988190b3ddd06d1f40dc78 |
completed | April 28, 2026, 9:39 p.m. |
| PD | Predicate disambiguation | batch_69e71b2ed7348190b6fa2e52f54393fb |
completed | April 21, 2026, 6:37 a.m. |
Created at: April 16, 2026, 8:30 p.m.