Triple
T12900802
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GNU ELPA |
E308603
|
entity |
| Predicate | alternativeTo |
P5887
|
FINISHED |
| Object | MELPA |
E308597
|
NE 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: MELPA | Statement: [GNU ELPA, alternativeTo, MELPA]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MELPA Context triple: [GNU ELPA, alternativeTo, MELPA]
-
A.
MELPA
chosen
MELPA is a popular community-maintained package repository for the Emacs text editor, offering a large collection of third-party extensions and tools.
-
B.
GNU ELPA
GNU ELPA is the official GNU Emacs Lisp Package Archive, providing a curated collection of free software packages for the Emacs editor.
-
C.
GNU ELPA (via external packages depending on it)
GNU ELPA (via external packages depending on it) is the official GNU Emacs package archive that distributes and manages a wide range of Emacs extensions and libraries.
-
D.
NonGNU ELPA
NonGNU ELPA is a package archive for the Emacs text editor that hosts free software packages not officially maintained as part of the GNU Emacs project.
-
E.
GitHub Packages
GitHub Packages is a software package hosting and management service integrated into GitHub, enabling developers to publish, share, and reuse packages alongside their source code and workflows.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97180ee708190b60a3e58c42f764f |
completed | April 10, 2026, 9:54 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f6cbbb199081909c32575097fbc2bf |
completed | May 3, 2026, 4:14 a.m. |
Created at: April 9, 2026, 5:40 p.m.