Triple
T4093837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Certified Analytics Professional |
E87765
|
entity |
| Predicate | isVendorSpecific |
P29440
|
FINISHED |
| Object | false |
—
|
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: false | Statement: [Certified Analytics Professional, isVendorSpecific, false]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVendorSpecific Context triple: [Certified Analytics Professional, isVendorSpecific, false]
-
A.
vendorSpecificTo
chosen
Indicates that something is tailored, restricted, or applicable only to a particular vendor or supplier, and not generally applicable across others.
-
B.
hasTypeOfVendor
Indicates that an entity is associated with or classified under a specific category or type of vendor.
-
C.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
D.
hasDataVendorCode
Indicates that an entity is associated with a specific vendor-assigned code used to identify its data source or provider.
-
E.
isSiteSpecific
Indicates that something is designed, intended, or valid only for a particular location, context, or site and does not generally apply elsewhere.
- 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_69aed94425148190be337845d56fac22 |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69aefcda2f408190bcf2b64535193162 |
completed | March 9, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69aef909c9c88190b09d48dad325a83c |
completed | March 9, 2026, 4:44 p.m. |
Created at: March 9, 2026, 3:40 p.m.