Triple
T35029773
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NonGNU ELPA |
E1010445
|
entity |
| Predicate | containsPackages |
P49317
|
FINISHED |
| Object | packages not officially maintained as part of GNU Emacs |
—
|
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: packages not officially maintained as part of GNU Emacs | Statement: [NonGNU ELPA, containsPackages, packages not officially maintained as part of GNU Emacs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsPackages Context triple: [NonGNU ELPA, containsPackages, packages not officially maintained as part of GNU Emacs]
-
A.
includesPackage
chosen
Indicates that one entity contains or comes bundled with a particular package as part of its composition or offering.
-
B.
hasPackageName
Indicates that an entity (such as a software component or module) is associated with a specific package name identifier.
-
C.
hasPackageType
Indicates that an entity is associated with or classified under a particular type or category of package.
-
D.
isPackageOf
Indicates that one entity is a package that contains, bundles, or delivers another entity.
-
E.
supportsBinaryPackages
Indicates that one entity provides or is compatible with precompiled binary packages for 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_69f76dccf0108190af43b465d3750196 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00a846a8f881908b073ad13a5af6ca |
completed | May 10, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_6a00a7aae194819085e1a2fd406f7922 |
completed | May 10, 2026, 3:43 p.m. |
Created at: May 3, 2026, 4:01 p.m.