Triple

T7987458
Position Surface form Disambiguated ID Type / Status
Subject RFC 2119 E185717 entity
Predicate title P38 FINISHED
Object Key words for use in RFCs to Indicate Requirement Levels E185717 NE FINISHED

How this triple was built (2 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: Key words for use in RFCs to Indicate Requirement Levels | Statement: [RFC 2119, title, Key words for use in RFCs to Indicate Requirement Levels]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Key words for use in RFCs to Indicate Requirement Levels
Context triple: [RFC 2119, title, Key words for use in RFCs to Indicate Requirement Levels]
  • A. RFC 2119 chosen
    RFC 2119 is an IETF document that defines the standard key words (like "MUST" and "SHOULD") used to indicate requirement levels in technical specifications.
  • B. RFCs
    RFCs (Requests for Comments) are a series of technical and organizational documents that define and standardize protocols, procedures, and policies for the Internet and related networks.
  • C. IETF Internet standards process
    The IETF Internet standards process is the formal, consensus-driven procedure by which the Internet Engineering Task Force develops, reviews, and approves technical specifications to become official Internet Standards.
  • D. IETF BCP series
    The IETF BCP series is a collection of Best Current Practice documents published by the Internet Engineering Task Force that define widely accepted technical and procedural guidelines for the Internet community.
  • E. RFC 1670
    RFC 1670 is an early Internet standards document related to network protocols that was later superseded by RFC 1901.
  • F. None of above.
  • G. Unsure - the case is ambiguous/there is not enough information to decide.

Provenance (3 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_69ca829a2cfc819083d591d58ec04075 completed March 30, 2026, 2:03 p.m.
NER Named-entity recognition batch_69cb3c4d11b08190aa13afb17155462c completed March 31, 2026, 3:15 a.m.
NED1 Entity disambiguation (via context triple) batch_69cbe0ed61588190b01423061acfce49 completed March 31, 2026, 2:57 p.m.
Created at: March 30, 2026, 5:15 p.m.