Triple
T7928186
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8314 |
E184119
|
entity |
| Predicate | updatesSecurityPracticesFor |
P11328
|
FINISHED |
| Object | email protocols |
—
|
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: email protocols | Statement: [RFC 8314, updatesSecurityPracticesFor, email protocols]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: updatesSecurityPracticesFor Context triple: [RFC 8314, updatesSecurityPracticesFor, email protocols]
-
A.
securityChangesAfter
Indicates that the security status or configuration of one entity is modified as a consequence of a prior event or change in another entity.
-
B.
securityRecommendation
chosen
Indicates that one entity advises or prescribes specific security-related actions, settings, or measures for another entity.
-
C.
securityProgram
Indicates that an entity is associated with, participates in, or is governed by a security program, such as a set of policies, controls, or initiatives related to safety or protection.
-
D.
safetyChangesImplemented
Indicates that specific safety-related modifications or measures have been put into effect.
-
E.
relatedSecurity
Indicates that one security has a defined relationship or association with another security, such as dependency, linkage, or relevance.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| PD | Predicate disambiguation | batch_69cae9335f288190ba96781fd6576a2b |
completed | March 30, 2026, 9:20 p.m. |
Created at: March 30, 2026, 5:07 p.m.