Triple
T5429709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Freedom Card smart card |
E121452
|
entity |
| Predicate | hasPaymentFunction |
P46101
|
FINISHED |
| Object | stored value |
—
|
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: stored value | Statement: [Freedom Card smart card, hasPaymentFunction, stored value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasPaymentFunction Context triple: [Freedom Card smart card, hasPaymentFunction, stored value]
-
A.
hasPaymentOption
chosen
Indicates that an entity supports or offers a particular method or option for making payments.
-
B.
hasPaymentModel
Indicates that an entity uses, is associated with, or operates under a particular payment model or pricing scheme.
-
C.
hasAdvancePaymentOption
Indicates that an entity offers the possibility to pay, in full or in part, before the corresponding goods or services are delivered or consumed.
-
D.
hasPayStatus
Indicates the current payment state or condition associated with an entity, such as whether an amount is paid, unpaid, pending, or otherwise resolved.
-
E.
canPayFor
Indicates that one entity has the ability or sufficient resources to cover the cost or expense 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_69bd463c65f0819082ee6483ab4b466a |
completed | March 20, 2026, 1:06 p.m. |
| NER | Named-entity recognition | batch_69bd8911a7348190ad9378a248190f07 |
completed | March 20, 2026, 5:51 p.m. |
| PD | Predicate disambiguation | batch_69bd846b8bdc81909dcdc2a3084226f2 |
completed | March 20, 2026, 5:31 p.m. |
Created at: March 20, 2026, 2:06 p.m.