Triple
T13636333
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Requirements for Internet Hosts – Communication Layers |
E325856
|
entity |
| Predicate | usesTerminologyFrom |
P79832
|
FINISHED |
| Object | RFC 2119 |
E185717
|
NE 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: RFC 2119 | Statement: [Requirements for Internet Hosts – Communication Layers, usesTerminologyFrom, RFC 2119]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2119 Context triple: [Requirements for Internet Hosts – Communication Layers, usesTerminologyFrom, RFC 2119]
-
A.
RFC 2119
chosen
RFC 2119 is an IETF document that defines the standard key words (like "MUST" and "SHOULD") used to indicate requirement levels in technical specifications.
-
B.
RFC 9293
RFC 9293 is the modern Internet standards document that consolidates and updates the core specification of the Transmission Control Protocol (TCP), replacing the original TCP specification defined in RFC 793.
-
C.
RFC 5639
RFC 5639 is an IETF standard document that specifies the Brainpool family of elliptic curves for use in cryptographic applications.
-
D.
RFC 3490
RFC 3490 is an Internet standard that defines Internationalized Domain Names in Applications (IDNA), enabling the use of non-ASCII characters in domain names.
-
E.
RFC 2195
RFC 2195 is an Internet standard that specifies the CRAM-MD5 authentication mechanism for secure password-based login in protocols like IMAP and POP3.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d8076beddc8190a53156f5bea77f5e |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc5a616dc81908b8c1213e1d4beed |
completed | April 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f78af297008190b12256c936714213 |
completed | May 3, 2026, 5:50 p.m. |
Created at: April 9, 2026, 9:51 p.m.