Triple
T1631422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 821 |
E35264
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object | RFC 2821 |
E34940
|
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 2821 | Statement: [RFC 821, obsoletedBy, RFC 2821]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2821 Context triple: [RFC 821, obsoletedBy, RFC 2821]
-
A.
RFC 5321
chosen
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
B.
RFC 821
RFC 821 is the original Internet standard that formally defined the Simple Mail Transfer Protocol (SMTP) for electronic mail transmission.
-
C.
RFC 3501
RFC 3501 is the Internet standard specification that defines version 4rev1 of the Internet Message Access Protocol (IMAP) used for accessing and managing email on a mail server.
-
D.
RFC 882
RFC 882 was an early Internet standard that originally specified the Domain Name System (DNS) protocol before being superseded by later RFCs such as RFC 1035.
-
E.
RFC 883
RFC 883 was an early Internet standard that originally specified the Domain Name System (DNS) before being superseded by later DNS specifications.
- 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_69a886036bc081909ff5de16dbe5e8ea |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69a909f5ae98819091ce5e00eb4256a2 |
completed | March 5, 2026, 4:43 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ad58d79bc88190bfc62f53dd8e8b90 |
completed | March 8, 2026, 11:09 a.m. |
Created at: March 4, 2026, 7:28 p.m.