Triple
T9427011
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Eras Tour |
E227282
|
entity |
| Predicate | ticketSalesCharacteristic |
P27056
|
FINISHED |
| Object | high demand |
—
|
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: high demand | Statement: [The Eras Tour, ticketSalesCharacteristic, high demand]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketSalesCharacteristic Context triple: [The Eras Tour, ticketSalesCharacteristic, high demand]
-
A.
ticketsSold
Indicates that a certain number of tickets have been purchased or distributed for a particular event or offering.
-
B.
ticketRevenueModel
Indicates the method or structure by which revenue is generated from ticket sales.
-
C.
salesCharacteristic
Indicates a defining feature, quality, or attribute associated with the sales of an entity, such as how, where, or under what conditions it is sold.
-
D.
ticketFormat
Indicates the specific structure, layout, or template in which a ticket is represented or issued.
-
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_69ca8436ba308190903e470776d2d893 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd7c91ba1c8190b8331fb1ba58cc61 |
completed | April 1, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69cca550777c819094e1851a6127cbbc |
completed | April 1, 2026, 4:55 a.m. |
Created at: March 30, 2026, 7:49 p.m.