Triple
T29031157
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | A11 Bionic |
E737728
|
entity |
| Predicate | CPUCoreTypeBig |
P34298
|
FINISHED |
| Object | Monsoon high-performance core |
—
|
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: Monsoon high-performance core | Statement: [A11 Bionic, CPUCoreTypeBig, Monsoon high-performance core]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: CPUCoreTypeBig Context triple: [A11 Bionic, CPUCoreTypeBig, Monsoon high-performance core]
-
A.
bigCoreCount
Indicates that an entity (such as a processor or system) has a relatively large number of cores compared to a typical or baseline configuration.
-
B.
CPUType
Indicates the specific model or category of processor architecture that an entity uses or is associated with.
-
C.
supportsBigLittleHybrid
Indicates that an entity is compatible with or enables operation using a big.LITTLE-style heterogeneous core or component configuration.
-
D.
l2CacheBigCores
Indicates that the relationship or action involves the L2 cache associated with the system’s big (high-performance) cores.
-
E.
hasCPUCore
chosen
Indicates that an entity (typically a computing device or processor) possesses or includes a specific CPU core 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_69f077ef00fc81909325f084ad37c035 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69f6603953f88190a8805a698456ab58 |
completed | May 2, 2026, 8:36 p.m. |
| PD | Predicate disambiguation | batch_69f659d297cc8190b2b962ba30a1edb3 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 9:55 a.m.