Triple
T22444428
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Node.js Package Maintenance Working Group |
E554829
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object |
Package Maintenance Working Group
The Package Maintenance Working Group is a Node.js community team focused on improving the health, sustainability, and maintenance practices of packages in the Node.js ecosystem.
|
E1537604
|
NE FINISHED |
How this triple was built (4 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: Package Maintenance Working Group | Statement: [Node.js Package Maintenance Working Group, shortName, Package Maintenance Working Group]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Package Maintenance Working Group Context triple: [Node.js Package Maintenance Working Group, shortName, Package Maintenance Working Group]
-
A.
Compliance and Interoperability Working Group
The Compliance and Interoperability Working Group is a technical body within the IBTA focused on ensuring that InfiniBand products from different vendors conform to specifications and operate seamlessly together.
-
B.
W3C Working Group
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
-
C.
W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
-
D.
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.
-
E.
W3C Interest Group
A W3C Interest Group is a community within the World Wide Web Consortium that brings together stakeholders to discuss and explore specific web-related topics without necessarily producing formal standards.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NEDg
Description generation
gpt-5.1
Instruction
Generate a one-sentence description of the target entity. You are given a context triple in the form (subject, predicate, object), where the object is the target entity. # Instructions Use the triple to infer relevant information about the entity. Describe the entity based on what is most defining, well-known. Avoid repeating the information from the triple, unless really essential. # Response Format Return only the sentence: "Description: [one-sentence description of the target entity]"
Input
Entity: Package Maintenance Working Group Triple: [Node.js Package Maintenance Working Group, shortName, Package Maintenance Working Group]
Generated description
The Package Maintenance Working Group is a Node.js community team focused on improving the health, sustainability, and maintenance practices of packages in the Node.js ecosystem.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Package Maintenance Working Group Target entity description: The Package Maintenance Working Group is a Node.js community team focused on improving the health, sustainability, and maintenance practices of packages in the Node.js ecosystem.
-
A.
Compliance and Interoperability Working Group
The Compliance and Interoperability Working Group is a technical body within the IBTA focused on ensuring that InfiniBand products from different vendors conform to specifications and operate seamlessly together.
-
B.
W3C Working Group
A W3C Working Group is a formal body within the World Wide Web Consortium that develops and maintains web standards and related technical reports through a consensus-driven process.
-
C.
W3C Coordination Group
The W3C Coordination Group is a World Wide Web Consortium body responsible for overseeing and harmonizing the work of various W3C groups to ensure technical consistency and effective collaboration across web standards.
-
D.
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.
-
E.
W3C Interest Group
A W3C Interest Group is a community within the World Wide Web Consortium that brings together stakeholders to discuss and explore specific web-related topics without necessarily producing formal standards.
- F. None of above. chosen
Provenance (5 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. |
| NED1 | Entity disambiguation (via context triple) | batch_6a0b0c74318081909fe8f6b794b6ce83 |
completed | May 18, 2026, 12:56 p.m. |
| NEDg | Description generation | batch_6a0b0d6d5b0c8190a96b3d556ccf5aee |
completed | May 18, 2026, 1 p.m. |
| NED2 | Entity disambiguation (via description) | batch_6a0b0e2082a88190b0c203cb933276dd |
completed | May 18, 2026, 1:03 p.m. |
Created at: April 16, 2026, 8:47 p.m.