Triple
T1777480
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 1901 |
E39212
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 1650
RFC 1650 is an early Internet standards document related to network management using SNMP that was later superseded by RFC 1901.
|
E220391
|
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 1650 | Statement: [RFC 1901, obsoletes, RFC 1650]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 1650 Context triple: [RFC 1901, obsoletes, RFC 1650]
-
A.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
B.
RFC 1450
RFC 1450 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
C.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
D.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
E.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
- 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 1650 Triple: [RFC 1901, obsoletes, RFC 1650]
Generated description
RFC 1650 is an early Internet standards document related to network management using SNMP that was later superseded by RFC 1901.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 1650 Target entity description: RFC 1650 is an early Internet standards document related to network management using SNMP that was later superseded by RFC 1901.
-
A.
RFC 1350
RFC 1350 is the Internet standards document that defines the Trivial File Transfer Protocol (TFTP), a simple protocol for transferring files over a network.
-
B.
RFC 1450
chosen
RFC 1450 is an early Internet standards document related to network management that was later superseded by RFC 1901.
-
C.
RFC 1906
RFC 1906 is an Internet standard that specifies the transport mappings for SNMPv2, detailing how SNMP messages are carried over various network protocols.
-
D.
RFC 1195
RFC 1195 is the IETF standard that extends the IS-IS routing protocol to support multiple network layer protocols, including IP.
-
E.
RFC 1725
RFC 1725 was an early Internet standard that originally defined the Post Office Protocol version 3 (POP3) for retrieving email from a mail server.
- F. None of above.
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_69ae0ab3a140819081dbb7b19e33051c |
completed | March 8, 2026, 11:48 p.m. |
| NEDg | Description generation | batch_69ae0b62dd048190acf6f9d76e5bfd47 |
completed | March 8, 2026, 11:50 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69ae0be695cc819093c237e19de9b731 |
completed | March 8, 2026, 11:53 p.m. |
Created at: March 4, 2026, 7:31 p.m.