Triple
T9075922
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Waterloo East |
E217482
|
entity |
| Predicate | isInContactlessPaymentArea |
P15672
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [London Waterloo East, isInContactlessPaymentArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInContactlessPaymentArea Context triple: [London Waterloo East, isInContactlessPaymentArea, yes]
-
A.
supportsTapToPay
chosen
Indicates that an entity enables or is compatible with tap-to-pay (contactless) payment functionality.
-
B.
hasNearbyPass
Indicates that an entity has at least one pass (e.g., transit or access pass) available within a short or locally defined distance from it.
-
C.
hasNFC
Indicates that one entity possesses or supports Near Field Communication (NFC) capability in relation to another entity or context.
-
D.
hasFarePaidArea
Indicates that an entity includes or is associated with a zone where access is restricted to users who have paid a fare.
-
E.
isWithinLondonFareSystem
Indicates that an entity (such as a station, stop, or route) is located inside the area covered by the London public transport fare system.
- 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_69ca83d6c14c8190bc056d927f00a2a2 |
completed | March 30, 2026, 2:08 p.m. |
| NER | Named-entity recognition | batch_69cc95c53274819099b3b3047bfe8cc8 |
completed | April 1, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69cc65fa79bc81908b46f05c8bba920f |
completed | April 1, 2026, 12:25 a.m. |
Created at: March 30, 2026, 7:12 p.m.