Triple
T4654741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Algol 68R |
E102381
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | dialect of Algol 68 |
C2955
|
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: dialect of Algol 68 Context triple: [Algol 68R, instanceOf, dialect of Algol 68]
-
A.
ALGOL family programming language
chosen
An ALGOL family programming language is a high-level, block-structured, imperative language descended from the original ALGOL designs, characterized by clear syntax, lexical scoping, and strong influence on later mainstream languages like Pascal, C, and Java.
-
B.
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.
-
C.
group of dialects
A group of dialects is a set of closely related language varieties that share common structural features and a historical or geographic connection within a larger language.
-
D.
Numic language
A Numic language is any member of a branch of the Uto-Aztecan language family spoken traditionally by Indigenous peoples of the Great Basin and surrounding regions of the western United States, including languages such as Northern Paiute, Shoshoni, and Comanche.
-
E.
Zenati language
The Zenati language is a conceptual class representing a branch of Berber languages characterized by shared phonological, morphological, and lexical features that distinguish it from other Afroasiatic language groups.
- 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_69bd43d823288190952279faa0d1d066 |
completed | March 20, 2026, 12:55 p.m. |
Created at: March 20, 2026, 1:14 p.m.