Triple

T22445403
Position Surface form Disambiguated ID Type / Status
Subject R^nRS E554850 entity
Predicate relatedTo P37 FINISHED
Object Scheme Request for Implementation — 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: Scheme Request for Implementation | Statement: [R^nRS, relatedTo, Scheme Request for Implementation]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Scheme Request for Implementation
Context triple: [R^nRS, relatedTo, Scheme Request for Implementation]
  • A. Global RfCs
    Global RfCs are Meta-Wiki-hosted community discussions where Wikimedia contributors from all projects and languages can propose and seek consensus on issues with global or cross-wiki impact.
  • B. Request for Comments 8259
    Request for Comments 8259 is an IETF standard that defines the JSON (JavaScript Object Notation) data interchange format, specifying its syntax and semantics for use in web and network applications.
  • C. Implementation Standards
    Implementation Standards are detailed requirements that guide internal auditors in applying the International Standards for the Professional Practice of Internal Auditing to specific types of engagements and situations.
  • D. Java Specification Request 173
    Java Specification Request 173 is the Java Community Process specification that defines the Streaming API for XML (StAX) for efficient, pull-based XML processing in Java.
  • E. Blueprint protocol
    Blueprint protocol is Bryan Johnson’s highly regimented longevity and health-optimization regimen that uses data-driven nutrition, exercise, sleep, and supplementation to slow biological aging.
  • 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: Scheme Request for Implementation
Target entity description: Scheme Request for Implementation (SRFI) is a community-driven process and collection of documents that propose, discuss, and standardize extensions and libraries for the Scheme programming language.
  • A. Global RfCs
    Global RfCs are Meta-Wiki-hosted community discussions where Wikimedia contributors from all projects and languages can propose and seek consensus on issues with global or cross-wiki impact.
  • B. Request for Comments 8259
    Request for Comments 8259 is an IETF standard that defines the JSON (JavaScript Object Notation) data interchange format, specifying its syntax and semantics for use in web and network applications.
  • C. Implementation Standards
    Implementation Standards are detailed requirements that guide internal auditors in applying the International Standards for the Professional Practice of Internal Auditing to specific types of engagements and situations.
  • D. Java Specification Request 173
    Java Specification Request 173 is the Java Community Process specification that defines the Streaming API for XML (StAX) for efficient, pull-based XML processing in Java.
  • E. Blueprint protocol
    Blueprint protocol is Bryan Johnson’s highly regimented longevity and health-optimization regimen that uses data-driven nutrition, exercise, sleep, and supplementation to slow biological aging.
  • F. None of above. chosen

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_69e11e5113208190ab58c6b595f9d1d0 completed April 16, 2026, 5:37 p.m.
NER Named-entity recognition batch_69f15b46e8ac8190bfa8c611ffcba822 completed April 29, 2026, 1:13 a.m.
Created at: April 16, 2026, 8:47 p.m.