Triple
T9931005
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | P2PE |
E192646
|
entity |
| Predicate | validationOutput |
P42634
|
FINISHED |
| Object | PCI-listed P2PE solution |
—
|
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-listed P2PE solution | Statement: [P2PE, validationOutput, PCI-listed P2PE solution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: validationOutput Context triple: [P2PE, validationOutput, PCI-listed P2PE solution]
-
A.
validatorType
Indicates the specific kind or category of validator associated with an entity or operation.
-
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.
supportsValidationOf
Indicates that one entity provides the mechanisms or conditions necessary for another entity to be checked or verified for correctness or compliance.
-
D.
valuationStatus
Indicates the current state or condition of an entity’s assessed value within a valuation process (e.g., pending, active, finalized, or invalid).
-
E.
confirmationOutcome
chosen
Indicates the result or status produced when a prior action, request, or assertion is checked and confirmed.
- 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_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. |
Created at: March 30, 2026, 8:43 p.m.