Triple
T33652894
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SAS Connect |
E862145
|
entity |
| Predicate | bookingCode |
P115602
|
FINISHED |
| Object | SK |
—
|
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: SK | Statement: [SAS Connect, bookingCode, SK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: bookingCode Context triple: [SAS Connect, bookingCode, SK]
-
A.
bookingCodeType
Indicates the type or category of a booking code used to classify or identify a reservation.
-
B.
bookingCodeLetter
chosen
Indicates the specific letter component used to identify or classify a booking within a booking code.
-
C.
ticketingCode
Indicates the specific fare or booking code associated with a ticket that defines its pricing, rules, and conditions of use.
-
D.
bookingControl
Indicates that one entity has the authority or mechanism to manage, modify, or regulate the booking or reservation of another entity.
-
E.
usesBookingCode
Indicates that one entity makes use of a specific booking code associated with another entity or transaction.
- 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_69f349840ba881908e3bfce536aeb92b |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:42 a.m.