Triple
T35612154
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tigerair Australia |
E1029063
|
entity |
| Predicate | ticketSalesEnded |
P183806
|
FINISHED |
| Object | 2020 |
—
|
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: 2020 | Statement: [Tigerair Australia, ticketSalesEnded, 2020]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketSalesEnded Context triple: [Tigerair Australia, ticketSalesEnded, 2020]
-
A.
ticketsSoldOutIn
Indicates that all available tickets for an event or offering have been fully sold within a specified time period or context.
-
B.
ticketsSold
Indicates that a certain number of tickets have been purchased or distributed for a particular event or offering.
-
C.
ticketSalesStart
Indicates the point in time when tickets for an event or service first become available for purchase.
-
D.
ticketingOutcome
Indicates the result or status produced by a ticketing process, such as whether a ticket was successfully issued, modified, or failed.
-
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_69f76e0653ec81909b1b813c126c6574 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:05 p.m.