Triple
T22876361
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Common Lisp the Language |
E567335
|
entity |
| Predicate | coversTopic |
P380
|
FINISHED |
| Object | Common Lisp sequences |
—
|
NE NERFINISHED |
How this triple was built (3 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: Common Lisp sequences | Statement: [Common Lisp the Language, coversTopic, Common Lisp sequences]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Common Lisp sequences Context triple: [Common Lisp the Language, coversTopic, Common Lisp sequences]
-
A.
Common Lisp
Common Lisp is a powerful, multi-paradigm dialect of the Lisp programming language standardised in the 1980s, known for its rich macro system, dynamic typing, and suitability for large-scale, extensible software systems.
-
B.
Common Lisp HyperSpec
The Common Lisp HyperSpec is an extensive, hyperlinked online reference that presents the full ANSI Common Lisp language standard in a searchable, web-friendly format.
-
C.
ANSI X3J13 Common Lisp
ANSI X3J13 Common Lisp is the standardized version of the Common Lisp programming language defined by the ANSI X3J13 committee, serving as the primary specification for compliant Common Lisp implementations.
-
D.
CLISP
CLISP is a portable, open-source implementation of the Common Lisp programming language featuring an interpreter, compiler, and extensive standard library support.
-
E.
Symbolics Common Lisp implementation
The Symbolics Common Lisp implementation is a specialized, high-performance version of the Common Lisp language designed for Symbolics Lisp machines, featuring advanced development tools and tight integration with the hardware and operating system.
- F. None of above. chosen
- G. Unsure - the case is ambiguous/there is not enough information to decide.
NED2
Entity disambiguation (via description)
gpt-5-mini-2025-08-07
Target entity: Common Lisp sequences Target entity description: Common Lisp sequences are an abstract data type in the Common Lisp language that uniformly encompasses ordered collections like lists and arrays, providing a rich set of generic operations for their manipulation.
-
A.
Common Lisp
Common Lisp is a powerful, multi-paradigm dialect of the Lisp programming language standardised in the 1980s, known for its rich macro system, dynamic typing, and suitability for large-scale, extensible software systems.
-
B.
Common Lisp HyperSpec
The Common Lisp HyperSpec is an extensive, hyperlinked online reference that presents the full ANSI Common Lisp language standard in a searchable, web-friendly format.
-
C.
ANSI X3J13 Common Lisp
ANSI X3J13 Common Lisp is the standardized version of the Common Lisp programming language defined by the ANSI X3J13 committee, serving as the primary specification for compliant Common Lisp implementations.
-
D.
CLISP
CLISP is a portable, open-source implementation of the Common Lisp programming language featuring an interpreter, compiler, and extensive standard library support.
-
E.
Symbolics Common Lisp implementation
The Symbolics Common Lisp implementation is a specialized, high-performance version of the Common Lisp language designed for Symbolics Lisp machines, featuring advanced development tools and tight integration with the hardware and operating system.
- F. None of above. chosen
Provenance (2 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_69e24589d8348190b96422d13a678bc1 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17f58a7308190b710bdf013e2e114 |
completed | April 29, 2026, 3:47 a.m. |
Created at: April 17, 2026, 3:39 p.m.