Triple
T27663709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Artifact Analysis |
E697180
|
entity |
| Predicate | usesVulnerabilitySource |
P38247
|
FINISHED |
| Object | OSV |
—
|
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: OSV | Statement: [Artifact Analysis, usesVulnerabilitySource, OSV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesVulnerabilitySource Context triple: [Artifact Analysis, usesVulnerabilitySource, OSV]
-
A.
vulnerabilitySource
Indicates that one entity is the origin, cause, or contributing factor of another entity’s vulnerability or weakness.
-
B.
associatedWithVulnerability
Indicates a relationship where an entity is linked to, affected by, or relevant to a specific vulnerability or security weakness.
-
C.
usesSourceType
chosen
Indicates that one entity makes use of, relies on, or operates based on a particular type or category of source.
-
D.
usesSigningSource
Indicates that one entity performs signing operations by relying on another specified source or mechanism for the signing process.
-
E.
usedAsSourceIn
Indicates that something serves as the origin, basis, or input from which another thing is derived, produced, or obtained.
- 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_69ef590b85a4819083ec7c12bd3c9c10 |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f64dbbaefc8190952b8320bf4397d8 |
completed | May 2, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69f64cacd2c08190aed8a1761d0da679 |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 27, 2026, 2:37 p.m.