Triple

T10623665
Position Surface form Disambiguated ID Type / Status
Subject RFC 8729 E250266 entity
Predicate focusesOn P31 FINISHED
Object IETF Stream of the RFC Series E49791 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: IETF Stream of the RFC Series | Statement: [RFC 8729, focusesOn, IETF Stream of the RFC Series]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IETF Stream of the RFC Series
Context triple: [RFC 8729, focusesOn, IETF Stream of the RFC Series]
  • A. 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.
  • B. 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.
  • C. IETF Internet Standards process changes
    IETF Internet Standards process changes are formal modifications to the procedures and rules governing how Internet standards are developed, reviewed, and approved within the Internet Engineering Task Force.
  • D. IETF Stream chosen
    The IETF Stream is the primary publication channel through which the Internet Engineering Task Force issues its technical standards and best current practice documents as RFCs.
  • E. RFC Series Working Group
    The RFC Series Working Group is an IETF body responsible for defining policies and processes that govern the publication and evolution of the Request for Comments (RFC) document series.
  • 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_69d6aa5993448190a493b790b8f85010 completed April 8, 2026, 7:19 p.m.
NER Named-entity recognition batch_69d6df7f11fc8190aed858f2e1443c08 completed April 8, 2026, 11:06 p.m.
NED1 Entity disambiguation (via context triple) batch_69d96b9a27f881908e451bfa6c118af4 completed April 10, 2026, 9:28 p.m.
Created at: April 8, 2026, 8:52 p.m.