Triple

T8283820
Position Surface form Disambiguated ID Type / Status
Subject Payment Application Data Security Standard E193742 entity
Predicate validationResult P42634 FINISHED
Object listing on PCI SSC List of Validated Payment Applications 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 on PCI SSC List of Validated Payment Applications | Statement: [Payment Application Data Security Standard, validationResult, listing on PCI SSC List of Validated Payment Applications]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: validationResult
Context triple: [Payment Application Data Security Standard, validationResult, listing on PCI SSC List of Validated Payment Applications]
  • A. valuationStatus
    Indicates the current state or condition of an entity’s assessed value within a valuation process (e.g., pending, active, finalized, or invalid).
  • B. validIn
    Indicates that a given entity, statement, or condition is applicable, correct, or legally/semantically acceptable within a specified context, scope, or domain.
  • C. confirmationOutcome chosen
    Indicates the result or status produced when a prior action, request, or assertion is checked and confirmed.
  • D. resultDetermination
    Indicates the process or criteria by which an outcome, decision, or result is established or concluded from given inputs or conditions.
  • E. result
    Indicates that one entity is produced, caused, or brought about as an outcome or consequence of another entity or process.
  • 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_69ca82e217a48190880695635c44b2ed completed March 30, 2026, 2:04 p.m.
NER Named-entity recognition batch_69cb7ad0535081908bb234cfc0e32b32 completed March 31, 2026, 7:42 a.m.
PD Predicate disambiguation batch_69cb70ad9fc081908741f8c4a4141edf completed March 31, 2026, 6:58 a.m.
Created at: March 30, 2026, 5:52 p.m.