Triple
T25425331
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Goldmont family |
E637102
|
entity |
| Predicate | intendedDeviceClass |
P19792
|
FINISHED |
| Object | embedded systems |
—
|
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: embedded systems | Statement: [Goldmont family, intendedDeviceClass, embedded systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: intendedDeviceClass Context triple: [Goldmont family, intendedDeviceClass, embedded systems]
-
A.
intendedEquipmentType
Indicates that a particular piece of equipment is the planned or designated type to be used in a given context or activity.
-
B.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
C.
roleOfDevice
Indicates that a device participates in a situation or system with a specified functional role or purpose.
-
D.
testedDeviceType
Indicates that one entity is the type or category of device on which another entity has been tested.
-
E.
primaryDeviceCategory
chosen
Indicates the main type or class of device associated with an entity or event, distinguishing it from other possible device categories.
- 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_69e75db58a1c8190891b9ff7c2f8414e |
completed | April 21, 2026, 11:21 a.m. |
| NER | Named-entity recognition | batch_69f621fcea1481909b6f8b3af1ee6820 |
completed | May 2, 2026, 4:10 p.m. |
| PD | Predicate disambiguation | batch_69f620dc38088190b56b2b15ed75b3c2 |
completed | May 2, 2026, 4:05 p.m. |
Created at: April 21, 2026, 1:57 p.m.