Triple

T1711890
Position Surface form Disambiguated ID Type / Status
Subject RFC 8017 E37200 entity
Predicate category P87 FINISHED
Object Internet Standards Track E35278 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: Internet Standards Track | Statement: [RFC 8017, category, Internet Standards Track]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: Internet Standards Track
Context triple: [RFC 8017, category, Internet Standards Track]
  • A. Internet Standard chosen
    An Internet Standard is a formal, widely implemented and stable technical specification approved by the Internet Engineering Task Force (IETF) as part of the core protocols and practices that define how the Internet operates.
  • B. Internet Engineering Steering Group
    The Internet Engineering Steering Group (IESG) is the body within the Internet Engineering Task Force responsible for technical management of IETF activities and the approval and publication of Internet standards.
  • 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 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. 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.
  • 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_69a8861912dc8190931af43b4b9158a7 completed March 4, 2026, 7:20 p.m.
NER Named-entity recognition batch_69aa6315afdc81908409435bb47e8ee0 completed March 6, 2026, 5:16 a.m.
NED1 Entity disambiguation (via context triple) batch_69ad8addf4a48190b19cdb861db5eecd completed March 8, 2026, 2:42 p.m.
Created at: March 4, 2026, 7:30 p.m.