Triple
T29343562
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ed Roberts |
E744099
|
entity |
| Predicate | usedProcessorInAltair8800 |
P166933
|
FINISHED |
| Object | Intel 8080 |
—
|
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: Intel 8080 | Statement: [Ed Roberts, usedProcessorInAltair8800, Intel 8080]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedProcessorInAltair8800 Context triple: [Ed Roberts, usedProcessorInAltair8800, Intel 8080]
-
A.
firstCommercialCPU
Indicates that the subject is the first central processing unit of its kind to be made available commercially.
-
B.
supportsApplesoftBASICPrograms
Indicates that an entity is capable of running, interpreting, or otherwise handling programs written in Applesoft BASIC.
-
C.
FPU
Indicates that one entity functions as or contains a floating-point unit responsible for performing arithmetic operations on non-integer (floating-point) numbers for another entity or within a system.
-
D.
suppliedMicroprocessorFor
chosen
Indicates that one entity provided or delivered a microprocessor to another entity for its use or integration.
-
E.
roleAtAtari
Indicates a person's specific role or position held at the company Atari.
- 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_69f674e06c9481909ed0ea736408f0d7 |
completed | May 2, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69f673c4abec8190bc2379e66f4af0a9 |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 28, 2026, 1:35 p.m.