Triple
T7928168
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 8314 |
E184119
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 3501 |
E39860
|
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 3501 | Statement: [RFC 8314, obsoletes, RFC 3501]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 3501 Context triple: [RFC 8314, obsoletes, RFC 3501]
-
A.
RFC 3501
chosen
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.
-
B.
RFC 2821
RFC 2821 is an earlier Internet standard that defined the Simple Mail Transfer Protocol (SMTP) for email transmission before being superseded by RFC 5321.
-
C.
RFC 822
RFC 822 is an early Internet standard that defines the format of text-based email messages, including headers and addressing conventions.
-
D.
RFC 5321
RFC 5321 is the Internet standard that specifies the Simple Mail Transfer Protocol (SMTP) used for email transmission across IP networks.
-
E.
RFC 1022
RFC 1022 is an early Internet standards document that was later superseded by RFC 1122, which more comprehensively defines host requirements for Internet protocols.
- 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_69ca828fe7bc819090f52c88dcd72183 |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cb3ac9ac4c819082cd2190fc3ce5a2 |
completed | March 31, 2026, 3:08 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cb5bfd08e88190bc6b2d77a148ae57 |
completed | March 31, 2026, 5:30 a.m. |
Created at: March 30, 2026, 5:07 p.m.