Triple
T36107348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | London Underground |
E1044395
|
entity |
| Predicate | integratedTicketingWith |
P52742
|
FINISHED |
| Object | National Rail |
—
|
NE NERFINISHED |
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: National Rail | Statement: [London Underground, integratedTicketingWith, National Rail]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratedTicketingWith Context triple: [London Underground, integratedTicketingWith, National Rail]
-
A.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
B.
hasTicketIntegration
chosen
Indicates that there is an established connection enabling ticket-related data or actions to be shared or synchronized between systems or components.
-
C.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
D.
usesIntegratedTicketValidAcrossOperators
Indicates that an entity uses a single integrated ticket that remains valid for travel across multiple transport operators.
-
E.
hasFareIntegration
Indicates that two or more transportation services or systems share a coordinated fare structure, allowing passengers to use a single ticket or payment arrangement across them.
- 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_69f76e338e2c8190b7f3bc68bec76349 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7b3e2f3c08190be4fd1ae4fa1266d |
completed | May 3, 2026, 8:45 p.m. |
| PD | Predicate disambiguation | batch_69f7b1bcc47081909fe7d592ac69006c |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:08 p.m.