Triple
T28583023
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ARM Cortex-A |
E723425
|
entity |
| Predicate | usesDesignModel |
P168976
|
FINISHED |
| Object | licensable IP 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: licensable IP cores | Statement: [ARM Cortex-A, usesDesignModel, licensable IP cores]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesDesignModel Context triple: [ARM Cortex-A, usesDesignModel, licensable IP cores]
-
A.
usedDesignFeature
Indicates that one entity employed or incorporated a particular design feature in its creation, implementation, or functionality.
-
B.
designModel
Indicates that one entity creates, specifies, or defines the structure or behavior of another entity as a model or blueprint.
-
C.
usedDesignDevice
Indicates that one entity employed or operated a particular design-related device or tool.
-
D.
hasDesign
Indicates that one entity possesses, embodies, or is characterized by a particular design associated with another entity.
-
E.
isDesignedAs
Indicates that something has been intentionally created or configured to serve as or function in the role of something else.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f67866e9248190b7ba218f9ca2ae8d |
completed | May 2, 2026, 10:19 p.m. |
| PD | Predicate disambiguation | batch_69f675fd59608190b246383435e68fce |
completed | May 2, 2026, 10:09 p.m. |
| PDg | Predicate description generation | batch_69f676c35f3481909b9ba18a5662d6ce |
completed | May 2, 2026, 10:12 p.m. |
Created at: April 28, 2026, 4:16 a.m.