Triple
T8950920
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 3530 |
E213343
|
entity |
| Predicate | obsoletedBy |
P101
|
FINISHED |
| Object |
RFC 7530
RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
|
E768630
|
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 7530 | Statement: [RFC 3530, obsoletedBy, RFC 7530]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 7530 Context triple: [RFC 3530, obsoletedBy, RFC 7530]
-
A.
RFC 7503
RFC 7503 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces RFC 5340 with revised specifications for the OSPFv3 routing protocol.
-
B.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
C.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
D.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
E.
RFC 7053
RFC 7053 is an Internet Engineering Task Force (IETF) standards document that refines and extends the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
- 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 7530 Triple: [RFC 3530, obsoletedBy, RFC 7530]
Generated description
RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 7530 Target entity description: RFC 7530 is the standards-track specification that updates and replaces the original NFS version 4 protocol definition, clarifying and refining the network file system’s core mechanisms.
-
A.
RFC 7503
RFC 7503 is an Internet Engineering Task Force (IETF) standards-track document that updates and replaces RFC 5340 with revised specifications for the OSPFv3 routing protocol.
-
B.
RFC 7950
RFC 7950 is the IETF specification that standardizes the YANG 1.1 data modeling language used for modeling configuration and state data in network management protocols.
-
C.
RFC 7539
RFC 7539 is an IETF standard that specifies the ChaCha20 stream cipher and the Poly1305 message authentication code for use in secure Internet protocols.
-
D.
RFC 7320
RFC 7320 is an Internet Engineering Task Force (IETF) document that provided guidelines and best practices for the use and management of URI registries in Internet protocols.
-
E.
RFC 7053
RFC 7053 is an Internet Engineering Task Force (IETF) standards document that refines and extends the Stream Control Transmission Protocol (SCTP) specification originally defined in RFC 4960.
- 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_69ca839843408190a39069a029a89f15 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc670c7244819084978922a9835bc9 |
completed | April 1, 2026, 12:30 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69cfc20a5ab481909e10f3abf679ec4c |
completed | April 3, 2026, 1:35 p.m. |
| NEDg | Description generation | batch_69cfc2d295c48190952486e6f44cd74f |
completed | April 3, 2026, 1:38 p.m. |
| NED2 | Entity disambiguation (via description) | batch_69cfc722921881908978147e4cc6875c |
completed | April 3, 2026, 1:56 p.m. |
Created at: March 30, 2026, 6:59 p.m.