Triple
T22710280
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Clozure CL |
E561572
|
entity |
| Predicate | isSuccessorOf |
P78
|
FINISHED |
| Object | MCL |
—
|
NE NERFINISHED |
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: MCL | Statement: [Clozure CL, isSuccessorOf, MCL]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: MCL Context triple: [Clozure CL, isSuccessorOf, MCL]
-
A.
MCL
MCL is a specialized postgraduate law degree at the University of Cambridge focused on corporate and commercial law.
-
B.
MCL
chosen
MCL (Macintosh Common Lisp) is an early Common Lisp development environment for the classic Mac OS known for its tight integration with the Macintosh user interface and tools.
-
C.
McL
McL is one of the 26 sporadic simple groups, known as the McLaughlin group, notable for its highly symmetric and exceptional finite group structure.
-
D.
LCL
LCL is the standard abbreviation for the Loeb Classical Library, a renowned series of books presenting classical Greek and Latin texts with facing-page English translations.
-
E.
LCL
LCL is a visual component framework used by the Lazarus IDE to build cross-platform graphical user interfaces in Free Pascal.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69f17907d7288190bb53f76974f95cef |
completed | April 29, 2026, 3:20 a.m. |
Created at: April 17, 2026, 3:17 p.m.