Triple
T1160438
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | npm |
E24478
|
entity |
| Predicate | packageRegistryURL |
P19956
|
FINISHED |
| Object | https://registry.npmjs.org/ |
—
|
LITERAL FINISHED |
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: https://registry.npmjs.org/ | Statement: [npm, packageRegistryURL, https://registry.npmjs.org/]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: packageRegistryURL Context triple: [npm, packageRegistryURL, https://registry.npmjs.org/]
-
A.
hasPackageRepository
chosen
Indicates that an entity is associated with or provides access to a specific software package repository.
-
B.
hasRepositoryMirror
Indicates that one repository serves as a mirrored copy or synchronized duplicate of another repository.
-
C.
repositoryLocation
Indicates the place or storage context where a repository is hosted, stored, or maintained.
-
D.
maintainsRegistryOf
Indicates that one entity is responsible for keeping and updating an official record or list of another set of entities or items.
-
E.
portOfRegistryFor
Indicates that one entity serves as the official port where another entity (typically a vessel) is registered.
- 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_69a494060e148190abb42f971242c197 |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bcaf3a9081908bad2eba74dffbc1 |
completed | March 1, 2026, 10:24 p.m. |
| PD | Predicate disambiguation | batch_69a4bb525b648190adcb7a29256d3c41 |
completed | March 1, 2026, 10:18 p.m. |
Created at: March 1, 2026, 7:45 p.m.