Triple
T28990454
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Shanghai Public Transportation Card |
E736010
|
entity |
| Predicate | canBeRefunded |
P101349
|
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: [Shanghai Public Transportation Card, canBeRefunded, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBeRefunded Context triple: [Shanghai Public Transportation Card, canBeRefunded, true]
-
A.
canBeRebatedTo
Indicates that a cost, fee, or amount is eligible to be refunded or credited back to a specified party.
-
B.
refundabilityType
Indicates the specific conditions or category under which something (typically a payment, ticket, or product) can be refunded.
-
C.
canBeRedeemedFor
Indicates that one item, asset, or benefit may be exchanged or converted to obtain another specified item, asset, or benefit.
-
D.
refundable
chosen
Indicates that an item, service, or payment can be returned or canceled in exchange for a reimbursement of money.
-
E.
canBeCancelled
Indicates that an action, event, or agreement is eligible to be terminated or revoked before completion.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fcda3699948190adb57625bae08091 |
completed | May 7, 2026, 6:30 p.m. |
| PD | Predicate disambiguation | batch_69fcd8fd16d08190b0aca6e19a632e99 |
completed | May 7, 2026, 6:25 p.m. |
Created at: April 28, 2026, 9:24 a.m.