Triple

T321629
Position Surface form Disambiguated ID Type / Status
Subject iSCSI E6426 entity
Predicate definedIn P775 FINISHED
Object RFC 3720
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
E51119 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 3720 | Statement: [iSCSI, definedIn, RFC 3720]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: RFC 3720
Context triple: [iSCSI, definedIn, RFC 3720]
  • A. RFC 3417
    RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
  • B. RFC 9002
    RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
  • 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 2419
    RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
  • E. RFC 4250
    RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
  • 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 3720
Triple: [iSCSI, definedIn, RFC 3720]
Generated description
RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: RFC 3720
Target entity description: RFC 3720 is the Internet Engineering Task Force (IETF) standard that specifies the Internet Small Computer Systems Interface (iSCSI) protocol for transporting SCSI commands over IP networks.
  • A. RFC 3417
    RFC 3417 is an Internet standard that specifies the transport mappings for the Simple Network Management Protocol (SNMP), defining how SNMP messages are carried over various network protocols such as UDP.
  • B. RFC 9002
    RFC 9002 is an IETF standard that specifies the loss detection and congestion control mechanisms for the QUIC transport protocol.
  • 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 2419
    RFC 2419 is an earlier Internet standard related to secure shell (SSH) protocols that was later superseded by RFC 4253.
  • E. RFC 4250
    RFC 4250 is an Internet Engineering Task Force (IETF) document that defines and registers protocol parameters and message numbers used by the Secure Shell (SSH) protocol suite.
  • 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_69a2e7933d6c8190bb2592ad13286ef2 completed Feb. 28, 2026, 1:03 p.m.
NER Named-entity recognition batch_69a2ea81a1e88190b3496070eb3d85f5 completed Feb. 28, 2026, 1:15 p.m.
NED1 Entity disambiguation (via context triple) batch_69a413ee31fc81908cbda4c0737d1b33 completed March 1, 2026, 10:24 a.m.
NEDg Description generation batch_69a414552e488190b02254f5c078eeb1 completed March 1, 2026, 10:26 a.m.
NED2 Entity disambiguation (via description) batch_69a41485f4048190b47a78d05fa775b1 completed March 1, 2026, 10:27 a.m.
Created at: Feb. 28, 2026, 1:08 p.m.