Triple
T28582645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCI CPoC |
E723416
|
entity |
| Predicate | assessmentResult |
P164654
|
FINISHED |
| Object | listing of approved CPoC solutions by PCI SSC |
—
|
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: listing of approved CPoC solutions by PCI SSC | Statement: [PCI CPoC, assessmentResult, listing of approved CPoC solutions by PCI SSC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: assessmentResult Context triple: [PCI CPoC, assessmentResult, listing of approved CPoC solutions by PCI SSC]
-
A.
assessment
Indicates an evaluation or judgment made about an entity’s quality, performance, or characteristics.
-
B.
assessmentName
Indicates the specific title or label assigned to an assessment within a system or context.
-
C.
assessmentNumber
Indicates the unique identifier or code assigned to a specific assessment instance or record.
-
D.
assessmentMethod
Indicates the method or procedure used to evaluate, measure, or judge something.
-
E.
assessmentBasis
Indicates the underlying criteria, evidence, or method used as the foundation for making an assessment or evaluation between entities.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f650cd6ee08190a5c05f83e4b95896 |
completed | May 2, 2026, 7:30 p.m. |
| PD | Predicate disambiguation | batch_69f64cb0d8008190912e1430cfaf92aa |
completed | May 2, 2026, 7:12 p.m. |
| PDg | Predicate description generation | batch_69f64db8ee1881909362701d72ffe282 |
completed | May 2, 2026, 7:17 p.m. |
Created at: April 28, 2026, 4:15 a.m.