Triple
T27053366
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datapoint 2200 |
E684837
|
entity |
| Predicate | intendedCpu |
P98650
|
FINISHED |
| Object | Intel 8008 |
—
|
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 8008 | Statement: [Datapoint 2200, intendedCpu, Intel 8008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedCpu Context triple: [Datapoint 2200, intendedCpu, Intel 8008]
-
A.
typicalCPU
Indicates that an entity uses or is associated with a standard or commonly used CPU for its type or category.
-
B.
isIntelBased
Indicates that something is built on, uses, or is derived from Intel technology, architecture, or components.
-
C.
primaryCpu
Indicates that one CPU is designated as the main or primary processing unit in relation to another component or system.
-
D.
CPUType
chosen
Indicates the specific model or category of processor architecture that an entity uses or is associated with.
-
E.
predecessorCpuArchitecture
Indicates that one CPU architecture directly precedes another in an evolutionary or historical development sequence.
- 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_69ef14829fac8190914bef9ecc3005d7 |
completed | April 27, 2026, 7:47 a.m. |
| NER | Named-entity recognition | batch_69f69edbb7648190bd89c57e0932eac1 |
completed | May 3, 2026, 1:03 a.m. |
| PD | Predicate disambiguation | batch_69f69d17e8d48190b30bcc2f4bd81eb2 |
completed | May 3, 2026, 12:55 a.m. |
Created at: April 27, 2026, 8:15 a.m.