Triple
T13551723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1812 |
E323663
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1009
RFC 1009 is an early Internet standards document that specified requirements and guidelines for IP routers before being superseded by later updates.
|
E1047318
|
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 1009 | Statement: [RFC 1812, obsoletes, RFC 1009]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1009 Context triple: [RFC 1812, obsoletes, RFC 1009]
-
A.
RFC 990
RFC 990 is an Internet standards document that updated and replaced RFC 870, refining technical specifications within the early TCP/IP protocol suite.
-
B.
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.
-
C.
RFC 1369
RFC 1369 is an early Internet standards document that specifies technical details related to network protocols and operations within the TCP/IP suite.
-
D.
RFC 1909
RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
-
E.
RFC 920
RFC 920 is an early Internet standards document that defines the procedures and requirements for registering and managing top-level domains in the Domain Name System (DNS).
- 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 1009 Triple: [RFC 1812, obsoletes, RFC 1009]
Generated description
RFC 1009 is an early Internet standards document that specified requirements and guidelines for IP routers before being superseded by later updates.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1009 Target entity description: RFC 1009 is an early Internet standards document that specified requirements and guidelines for IP routers before being superseded by later updates.
-
A.
RFC 990
RFC 990 is an Internet standards document that updated and replaced RFC 870, refining technical specifications within the early TCP/IP protocol suite.
-
B.
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.
-
C.
RFC 1369
RFC 1369 is an early Internet standards document that specifies technical details related to network protocols and operations within the TCP/IP suite.
-
D.
RFC 1909
RFC 1909 is an older Internet Engineering Task Force (IETF) Request for Comments document that was later superseded by RFC 3410 as part of the evolution of network management standards.
-
E.
RFC 920
RFC 920 is an early Internet standards document that defines the procedures and requirements for registering and managing top-level domains in the Domain Name System (DNS).
- 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_69d8076830b48190910a902bae5888e2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbaff0a6548190b8cde5084cef0061 |
completed | April 12, 2026, 2:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f75da721208190a3f5159125dbde9a |
completed | May 3, 2026, 2:37 p.m. |
| NEDg | Description generation | batch_69f75ec5101081909652b0c0998b36c8 |
completed | May 3, 2026, 2:42 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69f75f4a3b0c81908c0ca0351771953b |
completed | May 3, 2026, 2:44 p.m. |
Created at: April 9, 2026, 9:46 p.m.