Triple
T25932633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mantle |
E653472
|
entity |
| Predicate | targetHardwareVendor |
P76299
|
FINISHED |
| Object | AMD GPUs |
—
|
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: AMD GPUs | Statement: [Mantle, targetHardwareVendor, AMD GPUs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetHardwareVendor Context triple: [Mantle, targetHardwareVendor, AMD GPUs]
-
A.
supportsHardwareVendor
Indicates that one entity provides assistance, resources, or endorsement to a hardware vendor in fulfilling its products or services.
-
B.
targetVendorDevice
chosen
Indicates that a device is specifically associated with or designated as the target device for a particular vendor.
-
C.
technologyVendor
Indicates that one entity serves as the provider or supplier of technology products or services to another entity.
-
D.
architectureVendor
Indicates that one entity serves as the provider or supplier of architectural services, solutions, or products to another entity.
-
E.
manufacturerOfHardware
Indicates that an entity is the producer or maker of a specified hardware product or device.
- 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_69e7ab3eb9b881909c1390690551f868 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69f67c9fe7b48190b79b4041357edb49 |
completed | May 2, 2026, 10:37 p.m. |
| PD | Predicate disambiguation | batch_69f678cc272081909e5c70f1bc7407f0 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 22, 2026, 8:37 a.m.