Triple
T9901816
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2014 Winter Paralympics |
E182299
|
entity |
| Predicate | ticketSalesStart |
P91069
|
FINISHED |
| Object | 2013-09-27 |
—
|
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: 2013-09-27 | Statement: [2014 Winter Paralympics, ticketSalesStart, 2013-09-27]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketSalesStart Context triple: [2014 Winter Paralympics, ticketSalesStart, 2013-09-27]
-
A.
ticketsSold
Indicates that a certain number of tickets have been purchased or distributed for a particular event or offering.
-
B.
sellsTicketsUnder
Indicates that one entity sells tickets at a price lower than or under the pricing of another entity.
-
C.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
D.
bookingWindow
Indicates the time period before an event or service during which a booking or reservation can be made.
-
E.
ticketingLocation
Indicates the place or point where tickets are issued, sold, or otherwise processed for an event, service, or journey.
- 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_69ca82876f8081909cf75df0f99bb13f |
completed | March 30, 2026, 2:02 p.m. |
| NER | Named-entity recognition | batch_69cdb4e221448190b536742d1269f9d7 |
completed | April 2, 2026, 12:14 a.m. |
| PD | Predicate disambiguation | batch_69cd1d8c584081908b73de75eb18e438 |
completed | April 1, 2026, 1:28 p.m. |
| PDg | Predicate description generation | batch_69cd3581a9688190a00cef4c3eebb0ae |
completed | April 1, 2026, 3:10 p.m. |
Created at: March 30, 2026, 8:40 p.m.