Triple
T14789994
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | WCAP |
E347626
|
entity |
| Predicate | vendorSpecific |
P116114
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [WCAP, vendorSpecific, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vendorSpecific Context triple: [WCAP, vendorSpecific, true]
-
A.
vendorSpecificTo
Indicates that something is tailored, restricted, or applicable only to a particular vendor or supplier, and not generally applicable across others.
-
B.
vendorType
Indicates the classification or category of a vendor based on the type of goods or services they provide.
-
C.
osVendor
Indicates that one entity is the vendor or provider of an operating system associated with another entity.
-
D.
vendorDesignation
Indicates that one entity assigns or recognizes a specific vendor status, label, or role for another entity within a business or procurement context.
-
E.
vendorProductOf
Indicates that a product is offered or supplied by a particular vendor.
- 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_69d822e9b9e08190bedcc31a163fda82 |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69decaa1e9ec81908d7c26c1c4e43014 |
completed | April 14, 2026, 11:15 p.m. |
| PD | Predicate disambiguation | batch_69de8c090d1081909b5a9bf437499d6c |
completed | April 14, 2026, 6:48 p.m. |
| PDg | Predicate description generation | batch_69de90c5e3a08190868680b081308c1d |
completed | April 14, 2026, 7:08 p.m. |
Created at: April 10, 2026, 1:31 a.m.