Triple
T22710110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Allegro CL |
E561569
|
entity |
| Predicate | feature |
P374
|
FINISHED |
| Object | Metaobject Protocol |
—
|
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: Metaobject Protocol | Statement: [Allegro CL, feature, Metaobject Protocol]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Metaobject Protocol Context triple: [Allegro CL, feature, Metaobject Protocol]
-
A.
Meta-Object Facility
Meta-Object Facility is a standard meta-modeling framework defined by the Object Management Group for specifying, constructing, and managing technology-neutral metadata and models.
-
B.
Meta Object Facility
Meta Object Facility is an OMG standard for defining, manipulating, and integrating metadata and models, serving as a core foundation for model-driven engineering.
-
C.
The System of Objects
The System of Objects is a seminal 1968 work of critical theory by Jean Baudrillard that analyzes consumer goods as signs within a broader system of social meaning and everyday life.
-
D.
Objectory
Objectory is an object-oriented software development methodology created by Ivar Jacobson that introduced use cases and significantly shaped modern modeling approaches later incorporated into UML.
-
E.
Cecil: A Pure Object-Oriented Language with Multiple Dispatch and Multiple Inheritance
"Cecil: A Pure Object-Oriented Language with Multiple Dispatch and Multiple Inheritance" is a research programming language designed to explore flexible, purely object-oriented features such as multimethods, multiple inheritance, and dynamic dispatch mechanisms.
- 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: Metaobject Protocol Target entity description: The Metaobject Protocol is a reflective programming interface, most famously associated with the Common Lisp Object System (CLOS), that lets programmers customize and extend the language’s object system itself.
-
A.
Meta-Object Facility
Meta-Object Facility is a standard meta-modeling framework defined by the Object Management Group for specifying, constructing, and managing technology-neutral metadata and models.
-
B.
Meta Object Facility
Meta Object Facility is an OMG standard for defining, manipulating, and integrating metadata and models, serving as a core foundation for model-driven engineering.
-
C.
The System of Objects
The System of Objects is a seminal 1968 work of critical theory by Jean Baudrillard that analyzes consumer goods as signs within a broader system of social meaning and everyday life.
-
D.
Objectory
Objectory is an object-oriented software development methodology created by Ivar Jacobson that introduced use cases and significantly shaped modern modeling approaches later incorporated into UML.
-
E.
Cecil: A Pure Object-Oriented Language with Multiple Dispatch and Multiple Inheritance
"Cecil: A Pure Object-Oriented Language with Multiple Dispatch and Multiple Inheritance" is a research programming language designed to explore flexible, purely object-oriented features such as multimethods, multiple inheritance, and dynamic dispatch mechanisms.
- 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.