Triple
T12900459
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MELPA |
E308597
|
entity |
| Predicate | packageSubmission |
P63094
|
FINISHED |
| Object | pull requests on GitHub |
—
|
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: pull requests on GitHub | Statement: [MELPA, packageSubmission, pull requests on GitHub]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: packageSubmission Context triple: [MELPA, packageSubmission, pull requests on GitHub]
-
A.
submissionBy
Indicates that one entity is the submitter or originator of a particular submission associated with another entity.
-
B.
submissionSystem
chosen
Indicates a relationship where something is provided or turned in through a designated system or platform for receiving submissions.
-
C.
submissionBasis
Indicates the basis, criteria, or grounds on which something is submitted or filed (e.g., a document, application, or claim).
-
D.
submissionType
Indicates the specific category or format under which something is submitted (e.g., as a document, assignment, application, or other submission class).
-
E.
submittedTo
Indicates that one entity has formally sent or presented something (such as a document, request, or work) to another entity for consideration, review, or processing.
- 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_69d7bdf7c1f0819098102569a8d8cbf5 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d97180ee708190b60a3e58c42f764f |
completed | April 10, 2026, 9:54 p.m. |
| PD | Predicate disambiguation | batch_69d96fa776648190b9b5c30722ea50b6 |
completed | April 10, 2026, 9:46 p.m. |
Created at: April 9, 2026, 5:40 p.m.