Triple
T28582591
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PCI SPoC |
E723415
|
entity |
| Predicate | complianceListedOn |
P106894
|
FINISHED |
| Object | PCI SSC list of approved SPoC solutions |
—
|
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: PCI SSC list of approved SPoC solutions | Statement: [PCI SPoC, complianceListedOn, PCI SSC list of approved SPoC solutions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: complianceListedOn Context triple: [PCI SPoC, complianceListedOn, PCI SSC list of approved SPoC solutions]
-
A.
includesListedOn
Indicates that one entity contains or references another entity that is recorded or displayed on a specific list or listing.
-
B.
hasRegulatoryListing
chosen
Indicates that an entity is officially recorded or listed in a regulatory registry or listing maintained by an authority.
-
C.
typeOfComplianceBody
Indicates that one entity is a compliance-related body or authority of the type specified by the other entity.
-
D.
providesCompliance
Indicates that one entity supplies or ensures adherence to required rules, standards, or regulations for another entity.
-
E.
complianceInstrument
Indicates that one entity serves as a tool, mechanism, or measure used to ensure, demonstrate, or enforce compliance with a rule, standard, or obligation for another entity.
- 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_69f01d7f92e481909847f5f3f3174a89 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6978fe97081908fe568091ad9b159 |
completed | May 3, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69f69661e6ec8190948251c7516a32ad |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 28, 2026, 4:15 a.m.