Triple
T29343097
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Vector Graphic |
E744088
|
entity |
| Predicate | usedProcessorFamily |
P12004
|
FINISHED |
| Object | 8-bit microprocessors |
—
|
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: 8-bit microprocessors | Statement: [Vector Graphic, usedProcessorFamily, 8-bit microprocessors]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedProcessorFamily Context triple: [Vector Graphic, usedProcessorFamily, 8-bit microprocessors]
-
A.
supportsProcessorFamily
Indicates that one entity (such as hardware or software) is compatible with and can operate using a specified processor family.
-
B.
usesProcessorBrand
Indicates that one entity employs or is built with a processor manufactured by the specified brand.
-
C.
usesProcessorSeries
chosen
Indicates that one entity operates using, or is built to run on, a specific series or family of processors.
-
D.
cpuFamily
Indicates that one CPU belongs to, or is categorized under, a particular CPU family or architecture lineage.
-
E.
usedInComputerFamily
Indicates that something (such as a component, technology, or design) is employed within or forms part of a particular family or line of computers.
- 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_69f67257b0448190a13011af81c81449 |
completed | May 2, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
Created at: April 28, 2026, 1:34 p.m.