Triple
T9930955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Point-to-Point Encryption Standard |
E192645
|
entity |
| Predicate | validationProgram |
P91180
|
FINISHED |
| Object | PCI P2PE solution validation program |
—
|
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 P2PE solution validation program | Statement: [Point-to-Point Encryption Standard, validationProgram, PCI P2PE solution validation program]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validationProgram Context triple: [Point-to-Point Encryption Standard, validationProgram, PCI P2PE solution validation program]
-
A.
implementedProgram
Indicates that an entity has created, developed, or put into operation a particular program or software system.
-
B.
authorizesProgram
Indicates that one entity grants official permission for a particular program to exist, operate, or proceed.
-
C.
usedProgramModel
Indicates that an entity employed a specific program model as the basis or framework for its activities or operations.
-
D.
regulatesProgram
Indicates that one entity exercises control or governance over the operation, rules, or functioning of a program.
-
E.
establishedProgram
Indicates that an entity has created and put into operation a formal program that is now in an active, ongoing state.
- 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_69ca82dd978c8190947124ab0d3315ac |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cdb5b4196881909a004091a4203c45 |
completed | April 2, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cd1d90b8a8819081748f129c0c6ab6 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:43 p.m.