Triple
T22710335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Lisp Foundation (historical/related efforts) |
E561574
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | Common Lisp community initiative |
C8513
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: Common Lisp community initiative Context triple: [Common Lisp Foundation (historical/related efforts), instanceOf, Common Lisp community initiative]
-
A.
Lisp dialect
A Lisp dialect is a specific variant of the Lisp programming language family, defined by its own syntax, semantics, and standard libraries while retaining Lisp’s core features like symbolic expressions and homoiconicity.
-
B.
Lisp machine
A Lisp machine is a specialized computer system designed to efficiently run the Lisp programming language, featuring hardware and software tightly integrated around Lisp’s execution model.
-
C.
Clojure library
A Clojure library is a reusable collection of Clojure code, functions, and namespaces packaged to provide specific functionality that can be easily integrated into Clojure applications.
-
D.
free software community
chosen
A free software community is a collaborative group of users and developers who create, share, and improve software whose source code is openly available and can be freely used, modified, and redistributed.
-
E.
Haskell infrastructure project
A Haskell infrastructure project is a foundational software system, tooling, or service built in Haskell that supports, automates, or enhances the development, deployment, and operation of other Haskell applications.
- F. None of above.
Provenance (1 batch)
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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
Created at: April 17, 2026, 3:17 p.m.