Triple
T18501069
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bern public transport network |
E452065
|
entity |
| Predicate | integratesTicketingWith |
P52742
|
FINISHED |
| Object | regional rail services |
—
|
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: regional rail services | Statement: [Bern public transport network, integratesTicketingWith, regional rail services]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integratesTicketingWith Context triple: [Bern public transport network, integratesTicketingWith, regional rail services]
-
A.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
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.
hasTicketing
Indicates that an entity provides or is associated with a system or mechanism for issuing, managing, or selling tickets.
-
D.
ticketingScope
Indicates the range or domain within which ticketing actions (such as creation, assignment, or management of tickets) are valid or applicable.
-
E.
ticketingSystemOperator
Indicates that one entity operates, manages, or administers the ticketing system used for issuing, tracking, or processing tickets for another entity or 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_69d8d3855d50819097fc8561b0299dd9 |
completed | April 10, 2026, 10:40 a.m. |
| NER | Named-entity recognition | batch_69e532c43de48190b49b87c1bb591016 |
completed | April 19, 2026, 7:53 p.m. |
| PD | Predicate disambiguation | batch_69e469dbf5208190b6fc49e02a087f54 |
completed | April 19, 2026, 5:36 a.m. |
Created at: April 10, 2026, 11:36 a.m.