Triple
T32708719
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UserTransaction |
E836341
|
entity |
| Predicate | previousPackage |
P198114
|
FINISHED |
| Object | javax.transaction |
—
|
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: javax.transaction | Statement: [UserTransaction, previousPackage, javax.transaction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: previousPackage Context triple: [UserTransaction, previousPackage, javax.transaction]
-
A.
previousPackageTool
Indicates that one tool or package was used or applied immediately before another tool or package in a sequence of operations.
-
B.
previousNpmPackageName
Indicates that an entity was formerly known by a different npm package name before being renamed or replaced.
-
C.
currentPackage
Indicates the package that is presently active, selected, or in use in a given context or system.
-
D.
previousNamespace
Indicates that one namespace directly precedes or was used before another namespace, typically in a versioning or migration context.
-
E.
previousComponent
Indicates that one component directly precedes another in an ordered sequence or structure.
- F. None of above. chosen
Provenance (4 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fecb4d02f881909a9ee97ce98000d5 |
completed | May 9, 2026, 5:51 a.m. |
| PD | Predicate disambiguation | batch_69fec9846c1c8190b317f0711f0755db |
completed | May 9, 2026, 5:43 a.m. |
| PDg | Predicate description generation | batch_69fecb4be24481908bda6197d7fc32f4 |
completed | May 9, 2026, 5:51 a.m. |
Created at: May 1, 2026, 1:10 a.m.