Triple
T27780713
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCIP |
E699329
|
entity |
| Predicate | requiredExamVendor |
P12353
|
FINISHED |
| Object | Cisco Systems |
—
|
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: Cisco Systems | Statement: [CCIP, requiredExamVendor, Cisco Systems]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: requiredExamVendor Context triple: [CCIP, requiredExamVendor, Cisco Systems]
-
A.
examVendorAbbreviation
Indicates that an exam is associated with a vendor identified by a specific abbreviated name.
-
B.
certificationVendor
Indicates that an entity serves as the issuing or responsible vendor/organization for a particular certification associated with another entity.
-
C.
examProvider
chosen
Indicates that one entity is the organization or individual responsible for creating, administering, or supplying an exam to another entity.
-
D.
writtenExamRequiredBefore
Indicates that completing a written exam is a prerequisite that must occur before another specified action or event.
-
E.
eligibleVendors
Indicates that certain vendors meet the required criteria or conditions to be considered eligible for a specified purpose or process.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69fba78aca4c8190b8f1831e8cc04e06 |
completed | May 6, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69fba34a65a4819088bac6c17542d71c |
completed | May 6, 2026, 8:23 p.m. |
Created at: April 27, 2026, 5:09 p.m.