Triple
T16716780
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Moore School Lectures on computing |
E406244
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | historical event in computing |
C27133
|
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: historical event in computing Context triple: [Moore School Lectures on computing, instanceOf, historical event in computing]
-
A.
historical influence on computing
Historical influence on computing encompasses the people, events, technologies, and social forces from the past that have shaped the development, adoption, and evolution of computer systems and concepts over time.
-
B.
historical computer architecture
Historical computer architecture is the study and classification of past computer system designs, components, and organizational principles that shaped the evolution of computing hardware over time.
-
C.
historic event
chosen
A historic event is a significant occurrence in the past that has had a lasting impact on societies, cultures, or the course of history.
-
D.
pair of historical events
A pair of historical events is a conceptual grouping of two distinct occurrences from the past that are related by time, cause, theme, or contrast for purposes of comparison or analysis.
-
E.
historical event collection
A historical event collection is an organized set of documented occurrences from the past, grouped and structured to support analysis, comparison, and retrieval based on time, place, theme, or significance.
- 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_69d8838f242881908abd8bc138795886 |
completed | April 10, 2026, 4:58 a.m. |
Created at: April 10, 2026, 5:20 a.m.