Triple
T27730883
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UNIX wars |
E697426
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computing history event |
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: computing history event Context triple: [UNIX wars, instanceOf, computing history event]
-
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 system
A historical computer system is an early or past-generation computing platform, including its hardware, software, and operating environment, that illustrates the technological capabilities and design practices of its time.
-
C.
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.
-
D.
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.
-
E.
historical event date
A historical event date represents a specific calendar day on which a notable occurrence in history took place, serving as a temporal reference point for documenting and analyzing past events.
- 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_69ef590c3e288190ad54d2465af8ca4e |
completed | April 27, 2026, 12:39 p.m. |
Created at: April 27, 2026, 3:11 p.m.