Triple
T29343450
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Micro Instrumentation and Telemetry Systems |
E744097
|
entity |
| Predicate | usedCPU |
P85928
|
FINISHED |
| Object | Intel 8080 in Altair 8800 |
—
|
LITERAL FINISHED |
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: Intel 8080 in Altair 8800 | Statement: [Micro Instrumentation and Telemetry Systems, usedCPU, Intel 8080 in Altair 8800]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedCPU Context triple: [Micro Instrumentation and Telemetry Systems, usedCPU, Intel 8080 in Altair 8800]
-
A.
resourceUsage
Indicates how much of a particular resource is consumed or utilized by an entity, process, or activity over a given context or period.
-
B.
usedProcess
Indicates that an entity employed or applied a particular process to achieve a result or perform an action.
-
C.
typicalCPU
Indicates that an entity uses or is associated with a standard or commonly used CPU for its type or category.
-
D.
associatedWithCPU
chosen
Indicates a relationship where something is linked, connected, or related in function, use, or context to a CPU.
-
E.
totalCPUs
Indicates the total number of CPU units or cores allocated to or available for a given entity.
- F. None of above.
Provenance (3 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_69f09126cfcc8190899b16fbf3c2bf7b |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f66d7765208190b87b1cc6d96a151c |
completed | May 2, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
Created at: April 28, 2026, 1:35 p.m.