Triple
T26377225
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCS-4 |
E660932
|
entity |
| Predicate | hasCentralProcessingUnit |
P125913
|
FINISHED |
| Object | Intel 4004 |
—
|
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 4004 | Statement: [MCS-4, hasCentralProcessingUnit, Intel 4004]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCentralProcessingUnit Context triple: [MCS-4, hasCentralProcessingUnit, Intel 4004]
-
A.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
-
B.
cpu
Indicates that an entity functions as, contains, or is associated with a central processing unit (CPU) in a computational system.
-
C.
hasProcessingUnits
chosen
Indicates that an entity is equipped with or contains one or more processing units (such as CPUs, GPUs, or similar computational components).
-
D.
hasMicrocontrollerCore
Indicates that one entity incorporates or contains a microcontroller core as part of its internal components or architecture.
-
E.
hasMicrocontroller
Indicates that an entity contains, includes, or is equipped with a microcontroller as one of its components.
- 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_69ee812a698881908d6a58265995fa39 |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f66598d6008190a7ca8ff80399fd34 |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 26, 2026, 11:02 p.m.