Triple
T28610582
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MicroBlaze |
E724158
|
entity |
| Predicate | targetDeviceVendor |
P145864
|
FINISHED |
| Object | Xilinx |
—
|
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: Xilinx | Statement: [MicroBlaze, targetDeviceVendor, Xilinx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetDeviceVendor Context triple: [MicroBlaze, targetDeviceVendor, Xilinx]
-
A.
targetVendorDevice
Indicates that a device is specifically associated with or designated as the target device for a particular vendor.
-
B.
technologyVendor
Indicates that one entity serves as the provider or supplier of technology products or services to another entity.
-
C.
targetedDevice
Indicates that one entity is the specific device toward which another entity’s action, effect, or configuration is directed.
-
D.
vendorType
Indicates the classification or category of a vendor based on the type of goods or services they provide.
-
E.
targetPlatformManufacturer
chosen
Indicates that one entity is the manufacturer or producer of the platform targeted or used by another entity.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f7a225a77c81908f8953ccfeb14336 |
completed | May 3, 2026, 7:29 p.m. |
| PD | Predicate disambiguation | batch_69f7a06d4f108190bae3ab9ae431d2c7 |
completed | May 3, 2026, 7:22 p.m. |
Created at: April 28, 2026, 4:29 a.m.