Triple
T29246962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MOS Technology |
E741464
|
entity |
| Predicate | suppliedMicroprocessorFor |
P166933
|
FINISHED |
| Object | Apple I |
—
|
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: Apple I | Statement: [MOS Technology, suppliedMicroprocessorFor, Apple I]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliedMicroprocessorFor Context triple: [MOS Technology, suppliedMicroprocessorFor, Apple I]
-
A.
suppliedGPUFor
Indicates that one entity provided or furnished a GPU to another entity for its use or operation.
-
B.
microprocessorGeneration
Indicates the specific technological generation or iteration to which a given microprocessor belongs.
-
C.
cpuModel
Indicates the specific processor model associated with a given computing device or system.
-
D.
hasPowerSupplyType
Indicates that an entity is associated with a specific type or category of power supply it uses or requires.
-
E.
cpu
Indicates that an entity functions as, contains, or is associated with a central processing unit (CPU) in a computational system.
- F. None of above. chosen
Provenance (4 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664aa283c8190a869d0555eff60c6 |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f663362c008190a22afed262f1e426 |
completed | May 2, 2026, 8:48 p.m. |
| PDg | Predicate description generation | batch_69f6645a615481909b53d94512ecbaf1 |
completed | May 2, 2026, 8:53 p.m. |
Created at: April 28, 2026, 12:33 p.m.