Triple

T22444457
Position Surface form Disambiguated ID Type / Status
Subject Node.js Package Maintenance Working Group E554829 entity
Predicate relatedTo P37 FINISHED
Object Node.js Release Working Group — 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: Node.js Release Working Group | Statement: [Node.js Package Maintenance Working Group, relatedTo, Node.js Release Working Group]
NED1 Entity disambiguation (via context triple) gpt-5-mini-2025-08-07 
Target entity: Node.js Release Working Group
Context triple: [Node.js Package Maintenance Working Group, relatedTo, Node.js Release Working Group]
  • A. Node.js Package Maintenance Working Group
    The Node.js Package Maintenance Working Group is a community-driven team within the Node.js ecosystem that focuses on improving, supporting, and sustaining the health and maintenance of Node.js packages and their maintainers.
  • B. Node.js
    Node.js is an open-source, cross-platform runtime environment that allows developers to execute JavaScript code on the server side.
  • C. Mozilla JavaScript team
    The Mozilla JavaScript team is the group within Mozilla responsible for developing and maintaining the SpiderMonkey JavaScript engine used in Firefox and other Mozilla projects.
  • D. npm, Inc.
    npm, Inc. is the company behind the npm package manager and registry, a central infrastructure provider for JavaScript and Node.js developers.
  • E. Runtime Working Group
    The Runtime Working Group is a technical body within the Open Container Initiative responsible for defining and maintaining open industry standards for container runtime behavior and specifications.
  • 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: Node.js Release Working Group
Target entity description: The Node.js Release Working Group is a team within the Node.js project responsible for planning, managing, and executing the release process for Node.js versions, including scheduling, stability, and support timelines.
  • A. Node.js Package Maintenance Working Group
    The Node.js Package Maintenance Working Group is a community-driven team within the Node.js ecosystem that focuses on improving, supporting, and sustaining the health and maintenance of Node.js packages and their maintainers.
  • B. Node.js
    Node.js is an open-source, cross-platform runtime environment that allows developers to execute JavaScript code on the server side.
  • C. Mozilla JavaScript team
    The Mozilla JavaScript team is the group within Mozilla responsible for developing and maintaining the SpiderMonkey JavaScript engine used in Firefox and other Mozilla projects.
  • D. npm, Inc.
    npm, Inc. is the company behind the npm package manager and registry, a central infrastructure provider for JavaScript and Node.js developers.
  • E. Runtime Working Group
    The Runtime Working Group is a technical body within the Open Container Initiative responsible for defining and maintaining open industry standards for container runtime behavior and specifications.
  • 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_69f15ae517208190924a7968723f55ef completed April 29, 2026, 1:12 a.m.
Created at: April 16, 2026, 8:47 p.m.