Triple
T32709100
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | JavaMail |
E836349
|
entity |
| Predicate | usesPackageNamespace |
P177207
|
FINISHED |
| Object | javax.mail |
—
|
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.mail | Statement: [JavaMail, usesPackageNamespace, javax.mail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesPackageNamespace Context triple: [JavaMail, usesPackageNamespace, javax.mail]
-
A.
hasNamespace
Indicates that one entity is associated with, defined within, or belongs to a particular namespace context provided by another entity.
-
B.
codeNamespace
chosen
Indicates the namespace or modular grouping in which a piece of code or programming element is defined.
-
C.
includesPackage
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
D.
vendorNamespace
Indicates that something belongs to, is defined within, or is associated with a particular vendor’s designated namespace.
-
E.
isPackageOf
Indicates that one entity is a package that contains, bundles, or delivers another entity.
- 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_69f7b5ccbda481908fe1945c35e36ce8 |
completed | May 3, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f7b4c06f5881908f0b98cad6796478 |
completed | May 3, 2026, 8:49 p.m. |
Created at: May 1, 2026, 1:10 a.m.