Triple
T5014233
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rhônexpress |
E112700
|
entity |
| Predicate | ticketPurchaseOption |
P34227
|
FINISHED |
| Object | online |
—
|
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: online | Statement: [Rhônexpress, ticketPurchaseOption, online]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketPurchaseOption Context triple: [Rhônexpress, ticketPurchaseOption, online]
-
A.
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).
-
B.
bookingOption
Indicates a selectable arrangement or choice available for making a booking, such as a specific time, package, or set of conditions under which a reservation can be made.
-
C.
ticketPurchaseMethod
chosen
Indicates the method or channel through which a ticket was purchased (e.g., online, in person, via mobile app).
-
D.
ticketingCompatibleWith
Indicates that two systems, services, or components can interoperate or be used together within the same ticketing or reservation workflow without conflict.
-
E.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
- 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_69bd4434acb8819086679dbeccc2fe54 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd7310c5b08190a5c9ab0f9fe9569f |
completed | March 20, 2026, 4:17 p.m. |
| PD | Predicate disambiguation | batch_69bd714cbc448190aa53a8a83d768b64 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:35 p.m.