Triple
T32714094
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JSR 338 |
E836472
|
entity |
| Predicate | definesPackage |
P49317
|
FINISHED |
| Object | javax.persistence |
—
|
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: javax.persistence | Statement: [JSR 338, definesPackage, javax.persistence]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesPackage Context triple: [JSR 338, definesPackage, javax.persistence]
-
A.
alsoDefinedInPackage
Indicates that the same element or concept is additionally defined or declared in another software package.
-
B.
includesPackage
chosen
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
C.
isPackageOf
Indicates that one entity is a package that contains, bundles, or delivers another entity.
-
D.
notablePackage
Indicates that an entity is a particularly significant, well-known, or otherwise noteworthy package within its domain.
-
E.
typicalPackage
Indicates that something is the standard or commonly used package associated with a given entity or context.
- 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_69f3493446148190819541f3ffe79975 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fe0d165a48819098b854318a50d76c |
completed | May 8, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69fe0931002481908a95b34f95e9f64e |
completed | May 8, 2026, 4:02 p.m. |
Created at: May 1, 2026, 1:11 a.m.