Triple
T9136295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Orlandi Valuta |
E219212
|
entity |
| Predicate | currencyServiceType |
P87319
|
FINISHED |
| Object | cross-border remittances |
—
|
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: cross-border remittances | Statement: [Orlandi Valuta, currencyServiceType, cross-border remittances]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currencyServiceType Context triple: [Orlandi Valuta, currencyServiceType, cross-border remittances]
-
A.
currencyType
Indicates the specific kind of monetary unit or currency associated with an entity or transaction.
-
B.
currencyOnboard
Indicates that a particular currency has been enabled, registered, or made available for use within a given system or context.
-
C.
currencyProject
Indicates a relationship where a project is associated with, uses, or is denominated in a particular currency.
-
D.
currencyModel
Indicates that something uses, is based on, or conforms to a particular system or model of currency (e.g., monetary structure, denomination scheme, or valuation framework).
-
E.
currencyPlanned
Indicates that a specific currency is intended or scheduled to be used in a planned transaction, budget, or financial arrangement.
- F. None of above. chosen
Provenance (4 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_69ca83e012288190a5771058adbaabd2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cca8df68108190bb2df0583c5ad481 |
completed | April 1, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69cc6601d77881908299d58db6e64937 |
completed | April 1, 2026, 12:25 a.m. |
| PDg | Predicate description generation | batch_69cc6a3c78388190a7436acc0e44ff55 |
completed | April 1, 2026, 12:43 a.m. |
Created at: March 30, 2026, 7:18 p.m.