Triple
T29090046
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARMv8.2-M |
E734828
|
entity |
| Predicate | typicalImplementations |
P3697
|
FINISHED |
| Object | ARM Cortex-M CPU cores |
—
|
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: ARM Cortex-M CPU cores | Statement: [ARMv8.2-M, typicalImplementations, ARM Cortex-M CPU cores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalImplementations Context triple: [ARMv8.2-M, typicalImplementations, ARM Cortex-M CPU cores]
-
A.
commonlyImplementedBy
chosen
Indicates that the referenced item (e.g., a standard, interface, or pattern) is frequently realized or put into practice by the associated implementing entities.
-
B.
typicalInvocations
Indicates the usual or most common ways in which an action, function, or process is called, used, or carried out.
-
C.
commonlyImplementedWith
Indicates that one entity is typically realized, built, or carried out using the other as a standard or frequent implementation approach.
-
D.
areImplementedBy
Indicates that one entity serves as the concrete realization or execution of the specification, design, or interface defined by another entity.
-
E.
typicalInterface
Indicates that one entity serves as the standard or commonly used interface through which another entity is accessed or interacted 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_69f05b0ed66481908f2e864fa550d2f1 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_6a016cc5abcc8190b64094c777b40f6f |
completed | May 11, 2026, 5:44 a.m. |
| PD | Predicate disambiguation | batch_6a016b997ecc8190818207c57b9cbf17 |
completed | May 11, 2026, 5:39 a.m. |
Created at: April 28, 2026, 11:04 a.m.