Triple
T14790011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | iMIP |
E347627
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2447
RFC 2447 is an Internet standards document that originally specified how to integrate iCalendar-based scheduling with email using the iMIP protocol.
|
E1120155
|
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 2447 | Statement: [iMIP, obsoletes, RFC 2447]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2447 Context triple: [iMIP, obsoletes, RFC 2447]
-
A.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
B.
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.
-
C.
RFC 2446
RFC 2446 is an obsolete Internet standards document that originally specified the iCalendar Transport-Independent Interoperability Protocol (iTIP) for exchanging calendaring and scheduling information.
-
D.
RFC 1847
RFC 1847 is an early Internet standards document that defined a general framework for security multiparts in MIME email, laying groundwork for later secure messaging specifications.
-
E.
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.
- 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 2447 Triple: [iMIP, obsoletes, RFC 2447]
Generated description
RFC 2447 is an Internet standards document that originally specified how to integrate iCalendar-based scheduling with email using the iMIP protocol.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2447 Target entity description: RFC 2447 is an Internet standards document that originally specified how to integrate iCalendar-based scheduling with email using the iMIP protocol.
-
A.
RFC 2467
RFC 2467 is an Internet Engineering Task Force (IETF) standards document that originally specified aspects of IPv6 over certain network technologies before later being superseded by RFC 6557.
-
B.
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.
-
C.
RFC 2446
RFC 2446 is an obsolete Internet standards document that originally specified the iCalendar Transport-Independent Interoperability Protocol (iTIP) for exchanging calendaring and scheduling information.
-
D.
RFC 1847
RFC 1847 is an early Internet standards document that defined a general framework for security multiparts in MIME email, laying groundwork for later secure messaging specifications.
-
E.
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.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa1e9ec81908d7c26c1c4e43014 |
completed | April 14, 2026, 11:15 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69fe24bc8464819096b019f1e927d1a9 |
completed | May 8, 2026, 6 p.m. |
| NEDg | Description generation | batch_69fe27e699688190952b6a4b922e3294 |
completed | May 8, 2026, 6:13 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69fe2896057881908b3947d9649739e7 |
completed | May 8, 2026, 6:16 p.m. |
Created at: April 10, 2026, 1:31 a.m.