Triple
T9931670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MIME |
E192660
|
entity |
| Predicate | standardizedIn |
P7508
|
FINISHED |
| Object |
RFC 2045
RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
|
E830593
|
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 2045 | Statement: [MIME, standardizedIn, RFC 2045]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2045 Context triple: [MIME, standardizedIn, RFC 2045]
-
A.
RFC 1022
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
-
B.
RFC 1447
RFC 1447 is an early Internet standards document that specified mechanisms for managing SNMPv2 network management protocols before being superseded by later revisions.
-
C.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
D.
RFC 3821
RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
-
E.
RFC 3821
RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over IP networks.
- 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 2045 Triple: [MIME, standardizedIn, RFC 2045]
Generated description
RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2045 Target entity description: RFC 2045 is an Internet standard that defines the format and encoding rules for MIME message bodies used in email and related Internet protocols.
-
A.
RFC 1022
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
-
B.
RFC 1447
RFC 1447 is an early Internet standards document that specified mechanisms for managing SNMPv2 network management protocols before being superseded by later revisions.
-
C.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
D.
RFC 3821
RFC 3821 is an IETF standards document that specifies the Fibre Channel over TCP/IP (FCIP) protocol for transporting Fibre Channel frames over IP networks.
-
E.
RFC 3821
RFC 3821 is an Internet Engineering Task Force (IETF) standards document that specifies the Internet Fibre Channel Protocol (iFCP) for transporting Fibre Channel frames over IP networks.
- 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_69d228cab0fc81908ff5fad6916c1bab |
completed | April 5, 2026, 9:18 a.m. |
| NEDg | Description generation | batch_69d22990ef5881908b6a6100d7dcf6e6 |
completed | April 5, 2026, 9:21 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d22a0cb0808190a6119dc0268c50b9 |
completed | April 5, 2026, 9:23 a.m. |
Created at: March 30, 2026, 8:43 p.m.