Triple
T14442370
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitaca |
E358113
|
entity |
| Predicate | supportsElectronicMoney |
P89772
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Kitaca, supportsElectronicMoney, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsElectronicMoney Context triple: [Kitaca, supportsElectronicMoney, true]
-
A.
supportsMobileWallets
chosen
Indicates that an entity provides the capability to make or accept payments through mobile wallet services.
-
B.
hasDigitalWallet
Indicates that an entity possesses or is associated with a digital wallet for storing and managing digital payment instruments or assets.
-
C.
isFinancialMechanismFor
Indicates a relationship where one entity serves as the means, instrument, or structure through which another entity is financed, funded, or economically supported.
-
D.
legalTenderSupported
Indicates that a given currency or payment method is officially recognized and accepted as legal tender within a specified jurisdiction or context.
-
E.
supportsCardlessIdentification
Indicates that an entity enables identification or authentication of a person without requiring a physical card.
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915d28ec81909e72124e9dd67bfb |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:18 a.m.