Triple
T12900120
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TECO |
E308589
|
entity |
| Predicate | usedAsImplementationLanguageFor |
P102866
|
FINISHED |
| Object | early Emacs versions |
—
|
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: early Emacs versions | Statement: [TECO, usedAsImplementationLanguageFor, early Emacs versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedAsImplementationLanguageFor Context triple: [TECO, usedAsImplementationLanguageFor, early Emacs versions]
-
A.
languageOfImplementation
chosen
Indicates the programming language in which a given software system, component, or algorithm is implemented.
-
B.
implementedInLanguage
Indicates that a piece of software or code is written using a particular programming language.
-
C.
usedInProgrammingLanguages
Indicates that something (such as a concept, construct, or feature) is employed or implemented within one or more programming languages.
-
D.
developedForLanguage
Indicates that something (such as a tool, system, or resource) was specifically created or adapted to be used with a particular language.
-
E.
compilerLanguage
Indicates that one entity is the programming language in which a given compiler is implemented.
- 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.