Triple
T27780732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | CCIP |
E699329
|
entity |
| Predicate | credentialForm |
P6396
|
FINISHED |
| Object | professional certification credential |
—
|
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: professional certification credential | Statement: [CCIP, credentialForm, professional certification credential]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: credentialForm Context triple: [CCIP, credentialForm, professional certification credential]
-
A.
securityForm
Indicates a relationship where one entity serves as a security-related form or document associated with another entity, typically used to capture or manage security-relevant information or settings.
-
B.
credentialType
chosen
Indicates the specific kind or category of credential associated with an entity or relationship.
-
C.
formsPass
Indicates that one entity successfully completes or satisfies a required form or set of forms.
-
D.
inscriptionForm
Indicates the physical or structural form in which an inscription is presented (e.g., carved, painted, stamped, or otherwise rendered).
-
E.
credentialFramework
Indicates a formal system or structure within which a credential is defined, organized, or classified.
- 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_69f637ce6b688190813ef657673cb88d |
completed | May 2, 2026, 5:43 p.m. |
| PD | Predicate disambiguation | batch_69f6318ae6f08190b3f85f9201046a15 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 5:09 p.m.