Triple
T7928176
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8314 |
E184119
|
entity |
| Predicate | definesRequirement |
P39303
|
FINISHED |
| Object | mandatory encryption for email submission |
—
|
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: mandatory encryption for email submission | Statement: [RFC 8314, definesRequirement, mandatory encryption for email submission]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesRequirement Context triple: [RFC 8314, definesRequirement, mandatory encryption for email submission]
-
A.
establishedRequirement
chosen
Indicates that one entity has formally set or defined a requirement that another entity is expected to satisfy or comply with.
-
B.
typeOfRequirement
Indicates that one requirement is classified as a specific kind or category of another, more general requirement.
-
C.
dialogRequirement
Indicates that a certain condition, piece of information, or interaction must occur within a dialog or conversation for a related action, state, or process to proceed or be considered valid.
-
D.
typicalRequirement
Indicates that one entity is a standard or commonly expected prerequisite, condition, or necessity for another entity.
-
E.
evaluationRequirement
Indicates that one entity imposes or specifies conditions under which another entity must be assessed, tested, or evaluated.
- 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.