Triple
T24418752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | VN |
E615665
|
entity |
| Predicate | usedInPaymentSystems |
P21821
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [VN, usedInPaymentSystems, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedInPaymentSystems Context triple: [VN, usedInPaymentSystems, yes]
-
A.
paymentSystem
chosen
Indicates a relationship where one entity functions as a mechanism or platform through which another entity makes or processes payments.
-
B.
usedOnDenomination
Indicates that something (such as a material, feature, or design element) is applied to or associated with a particular denomination (e.g., value category of currency or similar units).
-
C.
paySystem
Indicates that one entity provides monetary or other compensation to another entity through a particular method, platform, or mechanism.
-
D.
usedFundingMethods
Indicates that an entity employed specific funding methods to finance an activity, project, or operation.
-
E.
isUsedForCoins
Indicates that something serves the function or purpose of holding, storing, or handling coins.
- 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_69e2d7e9bfac8190a748952a90957106 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f296a12a50819099fcdbc7096b53dd |
completed | April 29, 2026, 11:39 p.m. |
| PD | Predicate disambiguation | batch_69f287cc4fd4819081e93cc638d9512d |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 2:13 a.m.