Triple
T4504052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sapsan |
E101288
|
entity |
| Predicate | ticketClassSystem |
P56945
|
FINISHED |
| Object | multiple fare classes |
—
|
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: multiple fare classes | Statement: [Sapsan, ticketClassSystem, multiple fare classes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketClassSystem Context triple: [Sapsan, ticketClassSystem, multiple fare classes]
-
A.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
-
B.
ticketingCode
Indicates the specific fare or booking code associated with a ticket that defines its pricing, rules, and conditions of use.
-
C.
seatClass
Indicates the travel or seating category assigned to a passenger or seat (e.g., economy, business, first class).
-
D.
ticketingZoneType
Indicates the type or category of ticketing zone that applies within a given area or context.
-
E.
ticketingProduct
Indicates a relationship where an entity is associated with, or offered as, a ticketing-related product (such as a service or item used for issuing, managing, or selling tickets).
- 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_69bd43d175248190894dc58b5b395c26 |
completed | March 20, 2026, 12:55 p.m. |
| NER | Named-entity recognition | batch_69bd56fca7d4819081deb34628e04f00 |
completed | March 20, 2026, 2:17 p.m. |
| PD | Predicate disambiguation | batch_69bd521671688190bc655d25fa77eba2 |
completed | March 20, 2026, 1:56 p.m. |
| PDg | Predicate description generation | batch_69bd556b93cc8190ab817d2817109a0b |
completed | March 20, 2026, 2:10 p.m. |
Created at: March 20, 2026, 1:01 p.m.