Triple
T8697126
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 7540 |
E206428
|
entity |
| Predicate | bcp14KeywordsUsed |
P79832
|
FINISHED |
| Object | MUST, SHOULD, MAY as defined in RFC 2119 |
—
|
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: MUST, SHOULD, MAY as defined in RFC 2119 | Statement: [RFC 7540, bcp14KeywordsUsed, MUST, SHOULD, MAY as defined in RFC 2119]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bcp14KeywordsUsed Context triple: [RFC 7540, bcp14KeywordsUsed, MUST, SHOULD, MAY as defined in RFC 2119]
-
A.
hasBCPKeyword
Indicates that an entity is associated with, labeled by, or contains a specific BCP (Business Continuity Plan) keyword.
-
B.
basicMultilingualPlaneRange
Indicates that the referenced value or code point range lies within the Basic Multilingual Plane (BMP) of the Unicode character set.
-
C.
BCPFor
Indicates that something serves as the Business Continuity Plan (BCP) designated for a particular entity, process, or context.
-
D.
usesTerminologyFrom
chosen
Indicates that one entity adopts or incorporates the specialized terms or vocabulary originating from another entity or source.
-
E.
smtpCommandKeyword
Indicates that a given token or string functions as a recognized SMTP protocol command keyword in an email transmission session.
- 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_69ca83555b6c8190abe930dd397e863b |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc582b04688190a439135b08e20451 |
completed | March 31, 2026, 11:26 p.m. |
| PD | Predicate disambiguation | batch_69cc456bda508190a9aa0fb92760739e |
completed | March 31, 2026, 10:06 p.m. |
Created at: March 30, 2026, 6:34 p.m.