Triple
T30384161
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3821 |
E772902
|
entity |
| Predicate | BCP14KeywordsUsed |
P80194
|
FINISHED |
| Object | MUST |
—
|
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 | Statement: [RFC 3821, BCP14KeywordsUsed, MUST]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: BCP14KeywordsUsed Context triple: [RFC 3821, BCP14KeywordsUsed, MUST]
-
A.
hasBCPKeyword
chosen
Indicates that an entity is associated with, labeled by, or contains a specific BCP (Business Continuity Plan) keyword.
-
B.
smtpCommandKeyword
Indicates that a given token or string functions as a recognized SMTP protocol command keyword in an email transmission session.
-
C.
BCPFor
Indicates that something serves as the Business Continuity Plan (BCP) designated for a particular entity, process, or context.
-
D.
IANAExtensionType
Indicates that one entity is classified as a specific type or category of IANA extension associated with the other entity.
-
E.
registeredWithIANA
Indicates that an entity is officially recorded and recognized by the Internet Assigned Numbers Authority (IANA) in its registries.
- 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_69f2248e3444819081b05712dc6873de |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6851d7b288190a4d1d974e1f3ea16 |
completed | May 2, 2026, 11:13 p.m. |
| PD | Predicate disambiguation | batch_69f678d019fc8190913662cd2f87b857 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 8:01 p.m.