Triple
T27053365
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Datapoint 2200 |
E684837
|
entity |
| Predicate | originalCpuImplementation |
P83509
|
FINISHED |
| Object | discrete TTL logic |
—
|
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: discrete TTL logic | Statement: [Datapoint 2200, originalCpuImplementation, discrete TTL logic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalCpuImplementation Context triple: [Datapoint 2200, originalCpuImplementation, discrete TTL logic]
-
A.
firstFullyCustomCpuCoreBy
Indicates that the subject is the first fully custom CPU core ever designed or produced by the specified entity.
-
B.
cpuImplementation
chosen
Indicates that one entity serves as the hardware or architectural realization (implementation) of a specified CPU design or model.
-
C.
primaryCpu
Indicates that one CPU is designated as the main or primary processing unit in relation to another component or system.
-
D.
firstSupportedCPUCore
Indicates the CPU core that initially provided support or capability for a given feature, process, or entity.
-
E.
firstSupportedCPUFamily
Indicates the earliest CPU family that a system, software, or feature is designed to support or is compatible with.
- 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_69fd7b0503a08190ba07338365b6fcc9 |
completed | May 8, 2026, 5:56 a.m. |
| PD | Predicate disambiguation | batch_69fd7a9733dc81909199f453c0cc2bc1 |
completed | May 8, 2026, 5:54 a.m. |
Created at: April 27, 2026, 8:15 a.m.