Triple
T27780714
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCIP |
E699329
|
entity |
| Predicate | examVendorAbbreviation |
P163346
|
FINISHED |
| Object | Cisco |
—
|
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 | Statement: [CCIP, examVendorAbbreviation, Cisco]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: examVendorAbbreviation Context triple: [CCIP, examVendorAbbreviation, Cisco]
-
A.
examProvider
Indicates that one entity is the organization or individual responsible for creating, administering, or supplying an exam to another entity.
-
B.
examCode
Indicates a relationship where a specific code uniquely identifies or is assigned to an examination or test instance.
-
C.
coreExamName
Indicates the name or title assigned to a core examination within a given context or system.
-
D.
eligibleVendors
Indicates that certain vendors meet the required criteria or conditions to be considered eligible for a specified purpose or process.
-
E.
examType
Indicates the specific category or format of an exam associated with an assessment or testing event.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f637ce6b688190813ef657673cb88d |
completed | May 2, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
| PDg | Predicate description generation | batch_69f6359d46b88190922dd7de508e3b0e |
completed | May 2, 2026, 5:34 p.m. |
Created at: April 27, 2026, 5:09 p.m.