Triple
T4093819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Certified Analytics Professional |
E87765
|
entity |
| Predicate | isVendorNeutral |
P52982
|
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: [Certified Analytics Professional, isVendorNeutral, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isVendorNeutral Context triple: [Certified Analytics Professional, isVendorNeutral, true]
-
A.
isStandard
Indicates that something conforms to an established norm, specification, or commonly accepted rule.
-
B.
majorVendor
Indicates that one entity serves as a primary or leading supplier of goods or services to another entity.
-
C.
vendorSpecificTo
Indicates that something is tailored, restricted, or applicable only to a particular vendor or supplier, and not generally applicable across others.
-
D.
platformNeutral
Indicates that something is compatible with, applicable to, or designed to work across multiple platforms without dependence on any specific one.
-
E.
usesStandard
Indicates that one entity adopts, follows, or operates according to a specified standard defined by another entity or reference.
- 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_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. |
| PDg | Predicate description generation | batch_69aef9b34dec81909bbc3def9decc71a |
completed | March 9, 2026, 4:47 p.m. |
Created at: March 9, 2026, 3:40 p.m.