Triple
T10158203
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4510 |
E233823
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2251
RFC 2251 is an Internet standard that originally specified the version 3 protocol for the Lightweight Directory Access Protocol (LDAPv3) before being superseded by later LDAP specifications.
|
E845096
|
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 2251 | Statement: [RFC 4510, obsoletes, RFC 2251]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2251 Context triple: [RFC 4510, obsoletes, RFC 2251]
-
A.
RFC 2252
RFC 2252 is an earlier LDAP specification that defines attribute syntax and matching rules, later revised and superseded by RFC 4517.
-
B.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
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 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
E.
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.
- 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 2251 Triple: [RFC 4510, obsoletes, RFC 2251]
Generated description
RFC 2251 is an Internet standard that originally specified the version 3 protocol for the Lightweight Directory Access Protocol (LDAPv3) before being superseded by later LDAP specifications.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2251 Target entity description: RFC 2251 is an Internet standard that originally specified the version 3 protocol for the Lightweight Directory Access Protocol (LDAPv3) before being superseded by later LDAP specifications.
-
A.
RFC 2252
RFC 2252 is an earlier LDAP specification that defines attribute syntax and matching rules, later revised and superseded by RFC 4517.
-
B.
RFC 2571
RFC 2571 was an earlier specification in the Simple Network Management Protocol (SNMP) framework that was later superseded and updated by RFC 3411.
-
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 1651
RFC 1651 is an early Internet standards document that defined extensions to the Simple Mail Transfer Protocol (SMTP) to support enhanced email functionality.
-
E.
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.
- 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_69d300acae608190891d8f55c3d5102b |
completed | April 6, 2026, 12:39 a.m. |
| NEDg | Description generation | batch_69d302537a548190b211727dd124cba6 |
completed | April 6, 2026, 12:46 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69d3033245448190bcc802b7dbd274fc |
completed | April 6, 2026, 12:49 a.m. |
Created at: March 30, 2026, 9:09 p.m.