Triple
T9800657
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | PULSE network |
E237827
|
entity |
| Predicate | transactionMedium |
P27343
|
FINISHED |
| Object | payment cards |
—
|
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 cards | Statement: [PULSE network, transactionMedium, payment cards]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transactionMedium Context triple: [PULSE network, transactionMedium, payment cards]
-
A.
transactionNature
Indicates the type or character of a transaction, specifying what kind of exchange or operation is taking place between the involved parties.
-
B.
transactionModel
Indicates a relationship where an entity uses or is governed by a specific structured framework or schema for conducting, recording, or managing transactions.
-
C.
paymentSystem
Indicates a relationship where one entity functions as a mechanism or platform through which another entity makes or processes payments.
-
D.
turnBanking
Indicates that an entity is executing a turning maneuver that involves banking or tilting laterally, typically as part of directional change.
-
E.
transferType
chosen
Indicates the specific method or category of how something is transferred from one entity to another.
- 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_69ca84dd4608819097ff4ed00feca280 |
completed | March 30, 2026, 2:12 p.m. |
| NER | Named-entity recognition | batch_69cda62a11a88190880e0cce24923b14 |
completed | April 1, 2026, 11:11 p.m. |
| PD | Predicate disambiguation | batch_69cd03da45a88190b71b1be3354c15a6 |
completed | April 1, 2026, 11:39 a.m. |
Created at: March 30, 2026, 8:29 p.m.