Triple
T31601008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Câmara Interbancária de Pagamentos |
E806347
|
entity |
| Predicate | typeOfPaymentHandled |
P46101
|
FINISHED |
| Object | electronic funds transfers |
—
|
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: electronic funds transfers | Statement: [Câmara Interbancária de Pagamentos, typeOfPaymentHandled, electronic funds transfers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfPaymentHandled Context triple: [Câmara Interbancária de Pagamentos, typeOfPaymentHandled, electronic funds transfers]
-
A.
typeOfPaymentAffected
Indicates that a particular type or method of payment is impacted or influenced by a specified condition, event, or action.
-
B.
payType
Indicates the method or category of payment used in a transaction or compensation arrangement.
-
C.
paymentNetworkType
Indicates the type or category of payment network through which a payment is processed or routed.
-
D.
paymentMethod
Indicates the means or instrument through which a payment is made in a transaction.
-
E.
hasPaymentOption
chosen
Indicates that an entity supports or offers a particular method or option for making payments.
- 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_69f348d54ccc8190a03b5df9a2b40b25 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69fff328ddc0819080642334a41fcf95 |
completed | May 10, 2026, 2:53 a.m. |
| PD | Predicate disambiguation | batch_69fff2e0971c819081aa66f4a6a34b28 |
completed | May 10, 2026, 2:52 a.m. |
Created at: April 30, 2026, 10:32 p.m.