Triple

T1096663
Position Surface form Disambiguated ID Type / Status
Subject SCTP E24285 entity
Predicate originallyDefinedInRFC P10378 FINISHED
Object RFC 2960 E127656 NE FINISHED

How this triple was built (3 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: [SCTP, originallyDefinedInRFC, RFC 2960]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: RFC 2960
Context triple: [SCTP, originallyDefinedInRFC, RFC 2960]
  • A. RFC 4960 chosen
    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 3416
    RFC 3416 is an Internet standard that specifies the protocol operations for the Simple Network Management Protocol (SNMP), defining how management data is exchanged between network devices and management systems.
  • D. RFC 3415
    RFC 3415 is an Internet standard that specifies the View-based Access Control Model (VACM) for the Simple Network Management Protocol (SNMP), defining how access to management information is controlled.
  • E. RFC 3410
    RFC 3410 is an informational RFC that provides an overview, framework, and goals for the Simple Network Management Protocol version 3 (SNMPv3) and its related specifications.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
PD Predicate disambiguation gpt-5-mini-2025-08-07 
Target predicate: originallyDefinedInRFC
Context triple: [SCTP, originallyDefinedInRFC, RFC 2960]
  • A. originalRfc chosen
    Indicates that something is the initial or authoritative RFC (Request for Comments) document from which a specification, standard, or later revision originates.
  • B. originallyEnforcedBy
    Indicates that a rule, law, policy, or agreement was first implemented and upheld by a particular enforcing authority or agent.
  • C. onStandardsTrack
    Indicates that the subject is part of an officially recognized, actively developed standards process or pathway toward becoming a formal standard.
  • D. introducedInStandard
    Indicates that something (such as a concept, feature, or element) was first defined or formally specified in a particular standard.
  • E. conventionAdoptedAt
    Indicates that a convention was formally adopted or agreed upon at a specific event, meeting, or location.
  • F. None of above.

Provenance (4 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_69a4940542308190ac2a0b1f730b7cfc completed March 1, 2026, 7:31 p.m.
NER Named-entity recognition batch_69a4b99ffb3481908cd168b6c58e1c6d completed March 1, 2026, 10:11 p.m.
NED1 Entity disambiguation (via context triple) batch_69ac59a058b88190beb883bf35377316 completed March 7, 2026, 5 p.m.
PD Predicate disambiguation batch_69a4b7448c148190a3c9a4158ebd05b4 completed March 1, 2026, 10:01 p.m.
Created at: March 1, 2026, 7:42 p.m.