Triple
T10360598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4519 |
E244122
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 2256 |
E826112
|
NE FINISHED |
How this triple was built (2 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 2256 | Statement: [RFC 4519, obsoletes, RFC 2256]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2256 Context triple: [RFC 4519, obsoletes, RFC 2256]
-
A.
RFC 2256
chosen
RFC 2256 is an earlier LDAP (Lightweight Directory Access Protocol) schema specification that was later superseded by RFC 4517.
-
B.
RFC 2156
RFC 2156 is an Internet standards document that specifies the mapping between X.400 and RFC 822 (Internet) mail systems, updating and replacing earlier guidance on email interoperability.
-
C.
RFC 2766
RFC 2766 is an Internet Engineering Task Force (IETF) specification that originally defined Network Address Translation–Protocol Translation (NAT-PT) for IPv6–IPv4 interoperability before being superseded by later standards.
-
D.
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.
-
E.
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.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (3 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_69d381b22b8c8190aaed476be5f872a9 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4e9609c4481908b7d72ecf1adaa73 |
completed | April 7, 2026, 11:24 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d750b6ef248190bdbe16bbb8efcf88 |
completed | April 9, 2026, 7:09 a.m. |
Created at: April 6, 2026, 11:59 a.m.