Triple
T27681883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pnpm |
E697929
|
entity |
| Predicate | supportsPackageRegistry |
P19956
|
FINISHED |
| Object | npm registry |
—
|
NE NERFINISHED |
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: npm registry | Statement: [pnpm, supportsPackageRegistry, npm registry]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPackageRegistry Context triple: [pnpm, supportsPackageRegistry, npm registry]
-
A.
hasPackageRepository
chosen
Indicates that an entity is associated with or provides access to a specific software package repository.
-
B.
supportsBinaryPackages
Indicates that one entity provides or is compatible with precompiled binary packages for another entity.
-
C.
hasPackageSystem
Indicates that an entity uses or is associated with a particular package management system for installing, updating, or managing software components.
-
D.
supportsPackagingModel
Indicates that one entity provides compatibility with or functionality for a particular packaging model used by another entity.
-
E.
supportsRegistration
Indicates that an entity provides the capability or functionality to handle or accept registration actions or processes.
- F. None of above.
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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: April 27, 2026, 2:47 p.m.