Triple
T35029775
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NonGNU ELPA |
E1010445
|
entity |
| Predicate | programmingLanguageOfPackages |
P1592
|
FINISHED |
| Object | Emacs Lisp |
—
|
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: Emacs Lisp | Statement: [NonGNU ELPA, programmingLanguageOfPackages, Emacs Lisp]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programmingLanguageOfPackages Context triple: [NonGNU ELPA, programmingLanguageOfPackages, Emacs Lisp]
-
A.
programmingLanguageUsage
Indicates that an entity uses, is implemented in, or otherwise employs a particular programming language.
-
B.
packagingLanguage
Indicates the language used on or in the product’s packaging.
-
C.
programmingLanguage
chosen
Indicates that one entity is a programming language used to create, control, or interact with the other entity.
-
D.
usedByProgrammingLanguages
Indicates that something (such as a tool, library, paradigm, or feature) is employed or utilized by one or more programming languages.
-
E.
programLanguage
Indicates that an entity is implemented, written, or expressed using a particular programming language.
- 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_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4:01 p.m.