Triple
T27681931
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pnpm |
E697929
|
entity |
| Predicate | supportsNodeVersion |
P127933
|
FINISHED |
| Object | Node.js 16 and later (typical current support range) |
—
|
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: Node.js 16 and later (typical current support range) | Statement: [pnpm, supportsNodeVersion, Node.js 16 and later (typical current support range)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsNodeVersion Context triple: [pnpm, supportsNodeVersion, Node.js 16 and later (typical current support range)]
-
A.
supportsKubernetesVersion
Indicates that one entity is compatible with and able to run or work correctly with a specified Kubernetes version.
-
B.
supportsSinceVersion
chosen
Indicates that a given entity has provided support or compatibility for another entity starting from a specified version onward.
-
C.
supportsSemanticVersioning
Indicates that one entity adheres to and correctly handles semantic versioning rules for another entity’s versions.
-
D.
supportsSpecificationVersion
Indicates that one entity is compatible with and able to operate according to a particular version of a specification.
-
E.
requiresLanguageVersion
Indicates that one entity depends on or must use a specific version of a language in order to function or be considered valid.
- 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_69ffa9677be08190852c8ef6c2545fed |
completed | May 9, 2026, 9:38 p.m. |
| PD | Predicate disambiguation | batch_69ffa6570e2c8190a9d7b37f12b91d9a |
completed | May 9, 2026, 9:25 p.m. |
Created at: April 27, 2026, 2:47 p.m.