Triple
T32497977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | QSA program |
E830577
|
entity |
| Predicate | hasVersionAlignment |
P167528
|
FINISHED |
| Object | PCI DSS versions |
—
|
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 DSS versions | Statement: [QSA program, hasVersionAlignment, PCI DSS versions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVersionAlignment Context triple: [QSA program, hasVersionAlignment, PCI DSS versions]
-
A.
versionAlignedWith
chosen
Indicates that one entity’s version is synchronized, compatible, or intentionally matched with the version of another entity.
-
B.
hasAlignment
Indicates that one entity shares or exhibits a particular orientation, stance, or compatibility in relation to another entity or standard.
-
C.
hasAlignmentType
Indicates that an entity possesses a specific alignment category or classification, such as moral, structural, or directional alignment.
-
D.
hasVersionIn
Indicates that one entity exists as a specific version or variant within the context, format, or system represented by another entity.
-
E.
hasVersionBase
Indicates that one entity serves as the original or foundational version upon which another versioned entity is based.
- 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_69f349219cb8819087e120f509629c1b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7051ad6e4819095e82bbd64761803 |
completed | May 3, 2026, 8:19 a.m. |
| PD | Predicate disambiguation | batch_69f700fe24e08190998e2c96fbaaad38 |
completed | May 3, 2026, 8:02 a.m. |
Created at: May 1, 2026, 12:59 a.m.