Triple
T14343601
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | javax.crypto |
E355659
|
entity |
| Predicate | usesPackage |
P57997
|
FINISHED |
| Object | java.security |
—
|
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: java.security | Statement: [javax.crypto, usesPackage, java.security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPackage Context triple: [javax.crypto, usesPackage, java.security]
-
A.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
B.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
C.
hasPackageSystem
Indicates that an entity uses or is associated with a particular package management system for installing, updating, or managing software components.
-
D.
hasPackageName
chosen
Indicates that an entity (such as a software component or module) is associated with a specific package name identifier.
-
E.
usesClass
Indicates that one entity makes use of, depends on, or is implemented using a particular class in its structure or behavior.
- 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_69d82790a7e08190877e2d349b2e8d8e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de8e89ed9c8190acdb647ee618e919 |
completed | April 14, 2026, 6:59 p.m. |
| PD | Predicate disambiguation | batch_69de2a9958e881909d03ac03f135163e |
completed | April 14, 2026, 11:52 a.m. |
Created at: April 10, 2026, 1:14 a.m.