Triple
T21552431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple A10 Fusion |
E531795
|
entity |
| Predicate | firstAppleSoCWith |
P144211
|
FINISHED |
| Object | quad-core CPU |
—
|
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: quad-core CPU | Statement: [Apple A10 Fusion, firstAppleSoCWith, quad-core CPU]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstAppleSoCWith Context triple: [Apple A10 Fusion, firstAppleSoCWith, quad-core CPU]
-
A.
firstPublicReleaseDevice
Indicates that the subject is the device on which something (e.g., a product, feature, or software) was first publicly released.
-
B.
CPUType
Indicates the specific model or category of processor architecture that an entity uses or is associated with.
-
C.
firstCommercialCPU
Indicates that the subject is the first central processing unit of its kind to be made available commercially.
-
D.
firstSupportedMicroarchitecture
Indicates the earliest or oldest microarchitecture that provides support for a given hardware or software feature.
-
E.
appleSiliconGeneration
Indicates the specific Apple Silicon processor generation associated with or used by an entity.
- F. None of above. chosen
Provenance (4 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_69e0c460232c81908de2c3819d17c00e |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69eeb59375f481909d9e2b66d18c7c32 |
completed | April 27, 2026, 1:02 a.m. |
| PD | Predicate disambiguation | batch_69e6320766308190ba5dca2f7c826aa4 |
completed | April 20, 2026, 2:02 p.m. |
| PDg | Predicate description generation | batch_69e633bf34c481909925d8dc1a633a65 |
completed | April 20, 2026, 2:10 p.m. |
Created at: April 16, 2026, 6:29 p.m.