Triple
T10158291
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4516 |
E233825
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2255
RFC 2255 is an early Internet standard that defined the URL format for accessing LDAP directory services before being superseded by RFC 4516.
|
E846654
|
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 2255 | Statement: [RFC 4516, obsoletes, RFC 2255]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2255 Context triple: [RFC 4516, obsoletes, RFC 2255]
-
A.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 2256
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
E.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
- 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 2255 Triple: [RFC 4516, obsoletes, RFC 2255]
Generated description
RFC 2255 is an early Internet standard that defined the URL format for accessing LDAP directory services before being superseded by RFC 4516.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2255 Target entity description: RFC 2255 is an early Internet standard that defined the URL format for accessing LDAP directory services before being superseded by RFC 4516.
-
A.
RFC 2595
RFC 2595 is an Internet standard that originally defined the use of TLS to secure email-related protocols such as IMAP, POP3, and ACAP.
-
B.
RFC 2575
RFC 2575 is an earlier IETF standard that defined the View-based Access Control Model (VACM) for SNMP before being superseded by RFC 3415.
-
C.
RFC 2572
RFC 2572 is an earlier IETF specification that defined the Message Processing and Dispatching for the Simple Network Management Protocol (SNMP) before being superseded by RFC 3412.
-
D.
RFC 2256
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
E.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
- 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_69ca848e80748190b91d1e04d35512c7 |
completed | March 30, 2026, 2:11 p.m. |
| NER | Named-entity recognition | batch_69cdec5507f08190b47f797bacd5640c |
completed | April 2, 2026, 4:11 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d3176ac9388190bc76b3cffce93a3d |
completed | April 6, 2026, 2:16 a.m. |
| NEDg | Description generation | batch_69d31851a9c481908952592e6362b79f |
completed | April 6, 2026, 2:20 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d318c0cb8081909cfd53e586192ae7 |
completed | April 6, 2026, 2:21 a.m. |
Created at: March 30, 2026, 9:09 p.m.