Triple
T6408895
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RFC 4960 |
E127656
|
entity |
| Predicate | obsoletes |
P101
|
FINISHED |
| Object |
RFC 2960
RFC 2960 is the original specification that defined the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream communication.
|
E590631
|
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 2960 | Statement: [RFC 4960, obsoletes, RFC 2960]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RFC 2960 Context triple: [RFC 4960, obsoletes, RFC 2960]
-
A.
RFC 4960
RFC 4960 is the IETF standards document that specifies the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream, and multi-homed communication.
-
B.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
C.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
D.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
E.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
- 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 2960 Triple: [RFC 4960, obsoletes, RFC 2960]
Generated description
RFC 2960 is the original specification that defined the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream communication.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: RFC 2960 Target entity description: RFC 2960 is the original specification that defined the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream communication.
-
A.
RFC 4960
RFC 4960 is the IETF standards document that specifies the Stream Control Transmission Protocol (SCTP), a transport-layer protocol designed for message-oriented, multi-stream, and multi-homed communication.
-
B.
RFC 5340
RFC 5340 is the IETF specification that defines OSPF version 3, the link-state routing protocol for IPv6 networks.
-
C.
RFC 2060
RFC 2060 was the original specification of the Internet Message Access Protocol version 4 (IMAP4), defining how email clients access and manage messages on a mail server.
-
D.
RFC 3651
RFC 3651 is an IETF document that specifies the technical architecture and operational framework of the Handle System for assigning and resolving persistent digital identifiers.
-
E.
RFC 1452
RFC 1452 is an early Internet standards document that was later superseded by RFC 1901 as part of the evolution of network protocols.
- 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_69c0083723d88190b1e37b19df162c08 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068cdf25881908d42a5d979637ad6 |
completed | March 22, 2026, 10:10 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c638b38c888190aa2433173db64c90 |
completed | March 27, 2026, 7:58 a.m. |
| NEDg | Description generation | batch_69c63acb98588190b03c31eb3d8bdc35 |
completed | March 27, 2026, 8:07 a.m. |
| NED2 | Entity disambiguation (via description) | batch_69c63b334e608190b811b30e93199ac0 |
completed | March 27, 2026, 8:09 a.m. |
Created at: March 22, 2026, 4:41 p.m.