Triple
T3053407
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | BHM |
E60422
|
entity |
| Predicate | ticketCode |
P42683
|
FINISHED |
| Object | BHM |
—
|
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: BHM | Statement: [BHM, ticketCode, BHM]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketCode Context triple: [BHM, ticketCode, BHM]
-
A.
ticketingCode
chosen
Indicates the specific fare or booking code associated with a ticket that defines its pricing, rules, and conditions of use.
-
B.
ticket
Indicates that an entity serves as or is associated with a ticket, typically representing authorization, access, or a record for an event, service, or transaction.
-
C.
ticketClass
Indicates the category or level of service assigned to a ticket within a ticketing or reservation system.
-
D.
bookingCodeType
Indicates the type or category of a booking code used to classify or identify a reservation.
-
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.
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_69ad8578137c81908259dcb27c7d6d7c |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ad9bf51b5081908ce355a76cfa9e3c |
completed | March 8, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69ad962195388190856013a2519c2b0f |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 3:01 p.m.