Triple
T17568478
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Worldwide Developers Conference 2013 |
E427876
|
entity |
| Predicate | ticketSaleMethod |
P34227
|
FINISHED |
| Object | lottery system |
—
|
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: lottery system | Statement: [Apple Worldwide Developers Conference 2013, ticketSaleMethod, lottery system]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketSaleMethod Context triple: [Apple Worldwide Developers Conference 2013, ticketSaleMethod, lottery system]
-
A.
ticketPurchaseMethod
chosen
Indicates the method or channel through which a ticket was purchased (e.g., online, in person, via mobile app).
-
B.
ticketTypeSold
Indicates that a specific type of ticket has been sold in a given transaction or context.
-
C.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
D.
ticketsSold
Indicates that a certain number of tickets have been purchased or distributed for a particular event or offering.
-
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_69d889e0385081908a04b66f4dd4bd0d |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e4592f29d08190bc3de905d35af849 |
completed | April 19, 2026, 4:25 a.m. |
| PD | Predicate disambiguation | batch_69e3b4fd7d048190b54ee4c6155612a5 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:50 a.m.