Triple
T4362745
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Girobank |
E98697
|
entity |
| Predicate | paymentSystemType |
P21821
|
FINISHED |
| Object | giro system |
—
|
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: giro system | Statement: [Girobank, paymentSystemType, giro system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: paymentSystemType Context triple: [Girobank, paymentSystemType, giro system]
-
A.
paymentSystem
chosen
Indicates a relationship where one entity functions as a mechanism or platform through which another entity makes or processes payments.
-
B.
paySystem
Indicates that one entity provides monetary or other compensation to another entity through a particular method, platform, or mechanism.
-
C.
paymentMethod
Indicates the means or instrument through which a payment is made in a transaction.
-
D.
paymentEnvironment
Indicates the context or setting in which a payment is initiated, processed, or completed (such as online, in-store, or in-app).
-
E.
paySystemComparableTo
Indicates that one entity’s pay system is similar or equivalent in structure, level, or fairness to that 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_69b3454c772081908e20173e379e8ebe |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b351e5ee308190a9271e73689b4a2b |
completed | March 12, 2026, 11:53 p.m. |
| PD | Predicate disambiguation | batch_69b34f53e3cc8190bf5d4dbe2413bf65 |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:16 p.m.