Triple
T10050170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2554 |
E207724
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 4954 |
E212795
|
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 4954 | Statement: [RFC 2554, obsoletedBy, RFC 4954]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 4954 Context triple: [RFC 2554, obsoletedBy, RFC 4954]
-
A.
RFC 4954
chosen
RFC 4954 is an Internet standard that specifies the SMTP Authentication (SMTP AUTH) extension, enabling secure client authentication when sending email.
-
B.
RFC 5034
RFC 5034 is an Internet standard that extends the Post Office Protocol version 3 (POP3) to support Simple Authentication and Security Layer (SASL) mechanisms for enhanced email authentication and security.
-
C.
RFC 5214
RFC 5214 is an IETF standard that specifies the Intra-Site Automatic Tunnel Addressing Protocol (ISATAP) for transmitting IPv6 packets over IPv4 networks.
-
D.
RFC 1654
RFC 1654 is an early Internet standards document that specifies the Point-to-Point Protocol (PPP) for transmitting network layer datagrams over serial point-to-point links.
-
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.
- 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_69ca835ad0608190b7c80b292da004f5 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cdcf8e41c4819091fa12742197e207 |
completed | April 2, 2026, 2:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69d29a4064a48190b4fdb6bf3ea5af05 |
completed | April 5, 2026, 5:22 p.m. |
Created at: March 30, 2026, 8:56 p.m.