Triple
T8852464
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 2821 |
E210669
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object | RFC 1652 |
E230348
|
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 1652 | Statement: [RFC 2821, obsoletes, RFC 1652]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1652 Context triple: [RFC 2821, obsoletes, RFC 1652]
-
A.
RFC 1652
chosen
RFC 1652 is an early Internet standards document that defines the 8BITMIME extension for SMTP, enabling the transfer of 8-bit character data in email.
-
B.
RFC 1655
RFC 1655 is an early Internet standards document that specified the original Simple Network Management Protocol (SNMP) version 2 framework before being superseded by later revisions.
-
C.
RFC 1642
RFC 1642 is an Internet standards document that defines the UTF-7 encoding for representing Unicode characters in environments restricted to 7-bit data.
-
D.
RFC 1665
RFC 1665 is an early Internet standards document that was later superseded by RFC 1901 as the protocol specification evolved.
-
E.
RFC 1657
RFC 1657 is an early Internet standards document that defined SNMPv2 Management Information Base (MIB) extensions for managing BGP-4 routing protocol implementations.
- 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_69ca838a424c8190b1ecac115c2927e7 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60c3c5548190926e374bbe592180 |
completed | April 1, 2026, 12:03 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfd082bbe88190a207d39f9295735e |
completed | April 3, 2026, 2:36 p.m. |
Created at: March 30, 2026, 6:49 p.m.