Triple
T20878619
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Golden Ticket contest |
E514085
|
entity |
| Predicate | numberOfTickets |
P79948
|
FINISHED |
| Object | five |
—
|
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: five | Statement: [Golden Ticket contest, numberOfTickets, five]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: numberOfTickets Context triple: [Golden Ticket contest, numberOfTickets, five]
-
A.
ticketsSold
chosen
Indicates that a certain number of tickets have been purchased or distributed for a particular event or offering.
-
B.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
C.
ticketTypeSold
Indicates that a specific type of ticket has been sold in a given transaction or context.
-
D.
ticketQuota
Indicates a limit or allocation on the number of tickets that may be issued, held, or used within a specified context.
-
E.
ticketedAudience
Indicates that the audience for an event or activity is required to obtain tickets (i.e., attendance is controlled or limited via ticketing).
- 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_69e0b4f733f081908a401c0b7beb0b9f |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c6775f108190a79cd5e8c31cecf6 |
completed | April 21, 2026, 12:36 a.m. |
| PD | Predicate disambiguation | batch_69e5c9a8dc148190b33ff51894e2a8f9 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:45 p.m.