Triple

T22815304
Position Surface form Disambiguated ID Type / Status
Subject IETF mailing lists E565080 entity
Predicate governedBy P46 FINISHED
Object IETF IPR policies NE NERFINISHED

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: IETF IPR policies | Statement: [IETF mailing lists, governedBy, IETF IPR policies]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07
Target entity: IETF IPR policies
Context triple: [IETF mailing lists, governedBy, IETF IPR policies]
  • 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 governance
    IETF governance refers to the structures, processes, and decision-making practices that guide how the Internet Engineering Task Force develops, maintains, and evolves open internet standards.
  • C. 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.
  • D. Service Level Agreements for IANA functions
    Service Level Agreements for IANA functions are formal documents that define performance, reliability, and accountability standards for how ICANN delivers the Internet Assigned Numbers Authority’s core coordination services.
  • E. IETF Datatracker
    The IETF Datatracker is the official web-based system used by the Internet Engineering Task Force to manage, track, and publish documents, working group activities, and standards development progress.
  • F. None of above. chosen
  • G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2 Entity disambiguation (via description) gpt-5-mini-2025-08-07
Target entity: IETF IPR policies
Target entity description: IETF IPR policies are the formal rules and procedures that govern how intellectual property rights, such as patents, are disclosed, managed, and licensed in the development of Internet standards within the IETF.
  • 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 governance
    IETF governance refers to the structures, processes, and decision-making practices that guide how the Internet Engineering Task Force develops, maintains, and evolves open internet standards.
  • C. IETF BCP series chosen
    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.
  • D. Service Level Agreements for IANA functions
    Service Level Agreements for IANA functions are formal documents that define performance, reliability, and accountability standards for how ICANN delivers the Internet Assigned Numbers Authority’s core coordination services.
  • E. IETF Datatracker
    The IETF Datatracker is the official web-based system used by the Internet Engineering Task Force to manage, track, and publish documents, working group activities, and standards development progress.
  • F. None of above.

Provenance (2 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_69e2458426188190b58b8ab4844fe420 completed April 17, 2026, 2:36 p.m.
NER Named-entity recognition batch_69f17dcb872881909a031d8560635fce completed April 29, 2026, 3:40 a.m.
Created at: April 17, 2026, 3:33 p.m.