Triple
T27775942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Honeymoon Tour |
E699184
|
entity |
| Predicate | ticketSalesPerformance |
P27056
|
FINISHED |
| Object | mostly sold out shows |
—
|
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: mostly sold out shows | Statement: [The Honeymoon Tour, ticketSalesPerformance, mostly sold out shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketSalesPerformance Context triple: [The Honeymoon Tour, ticketSalesPerformance, mostly sold out shows]
-
A.
ticketsSold
Indicates that a certain number of tickets have been purchased or distributed for a particular event or offering.
-
B.
ticketSalesStart
Indicates the point in time when tickets for an event or service first become available for purchase.
-
C.
ticketTypeSold
Indicates that a specific type of ticket has been sold in a given transaction or context.
-
D.
ticketSalesReputation
Indicates the perceived quality or reliability of an entity based on its history or performance in selling tickets.
-
E.
ticketDemand
chosen
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
- 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_69ef6a4b5a9081909c9111396c2be3d2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f65876c52c8190bc889c7a67bd07f3 |
completed | May 2, 2026, 8:03 p.m. |
| PD | Predicate disambiguation | batch_69f6575d89788190aca478e4aea05a65 |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 27, 2026, 5:06 p.m.