Triple
T6970392
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | National Electronic Funds Transfer system |
E161583
|
entity |
| Predicate | supportsPaymentUseCase |
P15794
|
FINISHED |
| Object | salary payments |
—
|
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: salary payments | Statement: [National Electronic Funds Transfer system, supportsPaymentUseCase, salary payments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsPaymentUseCase Context triple: [National Electronic Funds Transfer system, supportsPaymentUseCase, salary payments]
-
A.
supportsTapToPay
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
B.
supportsUse
chosen
Indicates that one entity enables, allows, or is compatible with the use or operation of another entity.
-
C.
hasPaymentOption
Indicates that an entity supports or offers a particular method or option for making payments.
-
D.
supportsOpenLoopPayments
Indicates that an entity enables or is compatible with open-loop payment methods, where transactions are processed over general-purpose payment networks rather than a closed, proprietary system.
-
E.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense of another 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_69c68854a0d88190bc0bf82263f1afce |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6db1649288190a52c7dab57b3c7dc |
completed | March 27, 2026, 7:31 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c262508190a7708b3d9cf23d7c |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:30 p.m.