Triple
T8910953
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Blackfriars (via lines) |
E212178
|
entity |
| Predicate | supportsTicketing |
P3383
|
FINISHED |
| Object | Oyster |
—
|
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: Oyster | Statement: [London Blackfriars (via lines), supportsTicketing, Oyster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTicketing Context triple: [London Blackfriars (via lines), supportsTicketing, Oyster]
-
A.
hasTicketing
chosen
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
C.
hasTicketIntegration
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
-
D.
hasTicketingAuthority
Indicates that an entity possesses the official power or permission to issue, manage, or control tickets for an event, service, or system.
-
E.
primaryTicketingSystem
Indicates that one ticketing system is designated as the main or default system used for handling tickets in a given context.
- 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_69ca8393b1808190bd4336787ffa2c40 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc6523b9348190a7cefac9e73e2004 |
completed | April 1, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.