Triple
T32182633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Programmable Array Logic device |
E822026
|
entity |
| Predicate | hasConfigurationTechnology |
—
|
GENERATED |
| Object | fuse-based |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConfigurationTechnology Context triple: [Programmable Array Logic device, hasConfigurationTechnology, fuse-based]
-
A.
hasTechnologyPresence
Indicates that a particular technology exists, is implemented, or is actively in use within a given entity, context, or environment.
-
B.
hasTechnologySystem
Indicates that one entity possesses, utilizes, or is supported by a particular technology system.
-
C.
hasTechnicalElement
Indicates that something includes, involves, or is characterized by a technical component, feature, or aspect.
-
D.
hasNavigationTechnology
Indicates that an entity is equipped with or utilizes a system or technology for determining or guiding its position, route, or movement.
-
E.
hasConfiguration
Indicates that an entity is associated with or defined by a particular configuration or setup.
- F. None of above. chosen
Provenance (1 batch)
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_69f3490755288190aee11740a34862f9 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:34 a.m.