Triple
T22710230
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ECL |
E561571
|
entity |
| Predicate | supportsStandard |
P1587
|
FINISHED |
| Object | ANSI X3J13 Common Lisp |
—
|
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: ANSI X3J13 Common Lisp | Statement: [ECL, supportsStandard, ANSI X3J13 Common Lisp]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: ANSI X3J13 Common Lisp Context triple: [ECL, supportsStandard, ANSI X3J13 Common Lisp]
-
A.
CMU Common Lisp
CMU Common Lisp is a high-performance, open-source implementation of the Common Lisp programming language developed at Carnegie Mellon University, notable for its advanced compiler and optimization capabilities.
-
B.
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.
-
C.
Common Lisp Foundation (historical/related efforts)
The Common Lisp Foundation (historical/related efforts) was an initiative aimed at coordinating, promoting, and supporting the Common Lisp language and its community.
-
D.
Common Lisp Object System
Common Lisp Object System is the object-oriented programming subsystem of Common Lisp, providing multiple inheritance, generic functions, and a powerful metaobject protocol.
-
E.
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.
- 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: ANSI X3J13 Common Lisp Target entity description: 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.
-
A.
CMU Common Lisp
CMU Common Lisp is a high-performance, open-source implementation of the Common Lisp programming language developed at Carnegie Mellon University, notable for its advanced compiler and optimization capabilities.
-
B.
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.
-
C.
Common Lisp Foundation (historical/related efforts)
The Common Lisp Foundation (historical/related efforts) was an initiative aimed at coordinating, promoting, and supporting the Common Lisp language and its community.
-
D.
Common Lisp Object System
Common Lisp Object System is the object-oriented programming subsystem of Common Lisp, providing multiple inheritance, generic functions, and a powerful metaobject protocol.
-
E.
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.
- 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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178d1e24881909ebd4531c0daef7f |
completed | April 29, 2026, 3:19 a.m. |
Created at: April 17, 2026, 3:17 p.m.