Triple
T23425977
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Global Payments Inc. |
E560794
|
entity |
| Predicate | hasSecurityFocus |
P25437
|
FINISHED |
| Object | payment data security |
—
|
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: payment data security | Statement: [Global Payments Inc., hasSecurityFocus, payment data security]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecurityFocus Context triple: [Global Payments Inc., hasSecurityFocus, payment data security]
-
A.
hasSecuritySignificance
Indicates that something possesses importance or impact in the context of security, such as affecting safety, protection, or risk levels.
-
B.
hasSecurityPresence
Indicates that some form of security personnel, system, or measures are present at or associated with an entity or location.
-
C.
hasSecurityNotion
Indicates that one entity possesses, defines, or is associated with a particular concept or notion of security in relation to another entity or context.
-
D.
hasSecurityDimension
Indicates that something possesses or is associated with a particular aspect or dimension of security.
-
E.
hasSecurityConsideration
chosen
Indicates that there is a relevant security-related issue, risk, or precaution associated with the referenced 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_69e2454cb1108190ab21ada5411a7146 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1a54a28a08190add6184a44c5005b |
completed | April 29, 2026, 6:29 a.m. |
| PD | Predicate disambiguation | batch_69f061f92da081908e7f1d0cd1e9b01c |
completed | April 28, 2026, 7:30 a.m. |
Created at: April 17, 2026, 5:47 p.m.