Triple
T1777466
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1901 |
E39212
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1443
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
|
E205080
|
NE FINISHED |
How this triple was built (4 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 1443 | Statement: [RFC 1901, obsoletes, RFC 1443]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1443 Context triple: [RFC 1901, obsoletes, RFC 1443]
-
A.
RFC 1441
RFC 1441 is an early standards-track document in the Simple Network Management Protocol (SNMP) framework that was later superseded by RFC 1901 as the protocol evolved.
-
B.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
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.
-
E.
RFC 1533
RFC 1533 is an early Internet standards document that originally specified DHCP and BOOTP vendor extensions and options before being superseded by later updates.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: RFC 1443 Triple: [RFC 1901, obsoletes, RFC 1443]
Generated description
RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1443 Target entity description: RFC 1443 is an early Internet standards document that specified mechanisms for mapping between X.400 and RFC 822 email addressing and message formats.
-
A.
RFC 1441
RFC 1441 is an early standards-track document in the Simple Network Management Protocol (SNMP) framework that was later superseded by RFC 1901 as the protocol evolved.
-
B.
RFC 1813
RFC 1813 is the Internet Engineering Task Force (IETF) specification that defines version 3 of the Network File System (NFS) protocol.
-
C.
RFC 1094
RFC 1094 is the original specification document that standardizes the Network File System (NFS) protocol used for remote file access over a network.
-
D.
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.
-
E.
RFC 1533
RFC 1533 is an early Internet standards document that originally specified DHCP and BOOTP vendor extensions and options before being superseded by later updates.
- F. None of above. chosen
Provenance (5 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_69a88630519c8190a17addd83c4a3ef4 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69aa64b967f08190a73216361b9c2d83 |
completed | March 6, 2026, 5:23 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69adc9a14a18819090b83b3d10304c74 |
completed | March 8, 2026, 7:10 p.m. |
| NEDg | Description generation | batch_69adcaef04e88190a88f789a6370bafb |
completed | March 8, 2026, 7:15 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69adcb8e053c819082a3d4b36afe35be |
completed | March 8, 2026, 7:18 p.m. |
Created at: March 4, 2026, 7:31 p.m.