Triple
T2720851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oyster card |
E60075
|
entity |
| Predicate | rechargeMethod |
P5266
|
FINISHED |
| Object | ticket machines |
—
|
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: ticket machines | Statement: [Oyster card, rechargeMethod, ticket machines]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: rechargeMethod Context triple: [Oyster card, rechargeMethod, ticket machines]
-
A.
rechargeSource
Indicates that one entity serves as the power or energy provider used to recharge another entity.
-
B.
topUpMethod
chosen
Indicates the method or mechanism used to add funds or value to an account, balance, or service.
-
C.
paymentMethod
Indicates the means or instrument through which a payment is made in a transaction.
-
D.
rechargeRate
Indicates the rate or speed at which something restores or replenishes its capacity, energy, or resources over time.
-
E.
billingMethod
Indicates the way in which payment is arranged, processed, or charged for a product, service, or account.
- 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_69ab4b746d248190958e052045c09255 |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdab1cb808190b0789c76bc9cb090 |
completed | March 7, 2026, 7:58 a.m. |
| PD | Predicate disambiguation | batch_69abd8240920819087a812d816a55edb |
completed | March 7, 2026, 7:47 a.m. |
Created at: March 6, 2026, 9:55 p.m.