Triple
T13489346
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Berlin S-Bahn fare zone B |
E318591
|
entity |
| Predicate | ticketCombination |
P110602
|
FINISHED |
| Object | AB ticket |
—
|
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: AB ticket | Statement: [Berlin S-Bahn fare zone B, ticketCombination, AB ticket]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketCombination Context triple: [Berlin S-Bahn fare zone B, ticketCombination, AB ticket]
-
A.
ticketIncludes
Indicates that a particular ticket grants access to, contains, or covers the specified item, service, or component.
-
B.
ticketTypeExample
Indicates that an entity serves as an example or illustrative instance of a particular ticket type.
-
C.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
-
D.
companionTicketType
Indicates the type or category of ticket that is associated with or issued to a companion of a primary ticket holder.
-
E.
ticketTypeSold
Indicates that a specific type of ticket has been sold in a given transaction or context.
- F. None of above. chosen
Provenance (4 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_69d806b6bfec819089222715b2e86c8e |
completed | April 9, 2026, 8:06 p.m. |
| NER | Named-entity recognition | batch_69dbaf3cbe2081908c6792362c67c8f1 |
completed | April 12, 2026, 2:42 p.m. |
| PD | Predicate disambiguation | batch_69dbae06061881909a6a6032e0507587 |
completed | April 12, 2026, 2:36 p.m. |
| PDg | Predicate description generation | batch_69dbaecc98cc8190829f5be759c4f1e3 |
completed | April 12, 2026, 2:40 p.m. |
Created at: April 9, 2026, 9:43 p.m.