Triple
T8415020
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple A11 Bionic |
E198711
|
entity |
| Predicate | cpuCoreConfiguration |
P39131
|
FINISHED |
| Object | 2 high-performance cores and 4 efficiency cores |
—
|
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: 2 high-performance cores and 4 efficiency cores | Statement: [Apple A11 Bionic, cpuCoreConfiguration, 2 high-performance cores and 4 efficiency cores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cpuCoreConfiguration Context triple: [Apple A11 Bionic, cpuCoreConfiguration, 2 high-performance cores and 4 efficiency cores]
-
A.
CPUCoreConfiguration
chosen
Indicates the specific arrangement and characteristics of processor cores allocated or defined within a computing system.
-
B.
coreCountCPU
Indicates the number of processing cores that a CPU has.
-
C.
gpuCoreCount
Indicates the number of processing cores present in a GPU.
-
D.
hasCPUCore
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core as one of its components.
-
E.
cpuCoreMicroarchitecture
Indicates the specific microarchitecture design implemented in a given CPU core.
- 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_69ca831201b481909e137936ef99ff11 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cb83e443a08190983d9a0a61e0f781 |
completed | March 31, 2026, 8:20 a.m. |
| PD | Predicate disambiguation | batch_69cb70d70ea081909c3dc1bd2ec14f85 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:06 p.m.