Triple
T9931673
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIME |
E192660
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object |
RFC 2048
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
|
E831060
|
NE FINISHED |
How this triple was built (4 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 2048 | Statement: [MIME, standardizedIn, RFC 2048]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2048 Context triple: [MIME, standardizedIn, RFC 2048]
-
A.
RFC 2440
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
B.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 2048 Triple: [MIME, standardizedIn, RFC 2048]
Generated description
RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2048 Target entity description: RFC 2048 is an Internet standards document that defines the registration procedures and guidelines for MIME media types and related parameters.
-
A.
RFC 2440
RFC 2440 is the Internet Engineering Task Force (IETF) specification that defines the OpenPGP message format for encrypted and signed data.
-
B.
RFC 2449
RFC 2449 is an Internet standards document that extends the POP3 email protocol with additional capabilities and commands to improve flexibility and interoperability.
-
C.
RFC 2487
RFC 2487 is an Internet standards document that originally defined the STARTTLS extension for securing SMTP connections with TLS, later superseded by RFC 3207.
-
D.
RFC 2419
RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
-
E.
RFC 3948
RFC 3948 is an IETF standard that specifies how to encapsulate IPsec ESP packets over UDP to enable IPsec traversal through NAT devices.
- F. None of above. chosen
Provenance (5 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b54f348190b8e70e7beff6098a |
completed | April 2, 2026, 12:17 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d228d1620c8190ac7125b268dd6832 |
completed | April 5, 2026, 9:18 a.m. |
| NEDg | Description generation | batch_69d22c3a6fc0819083a376736325a04e |
completed | April 5, 2026, 9:32 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d22cabf39881908f45667751384df5 |
completed | April 5, 2026, 9:34 a.m. |
Created at: March 30, 2026, 8:43 p.m.