Triple
T20221282
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple WWDC 2018 |
E495259
|
entity |
| Predicate | approximateTicketPriceUSD |
P30527
|
FINISHED |
| Object | 1599 |
—
|
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: 1599 | Statement: [Apple WWDC 2018, approximateTicketPriceUSD, 1599]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: approximateTicketPriceUSD Context triple: [Apple WWDC 2018, approximateTicketPriceUSD, 1599]
-
A.
salePriceApproximate
chosen
Indicates that the recorded sale price is an estimated or approximate value rather than an exact amount.
-
B.
directPaymentAmountPerAdultUSD
Indicates the amount of a direct payment, expressed in U.S. dollars, that is allocated to each adult.
-
C.
estimatedTheater
Indicates that one entity has calculated or predicted the theater-related value (such as revenue, attendance, or performance metrics) associated with another entity.
-
D.
ticketPricePlanned
Indicates that a ticket has an intended or scheduled price set in advance, as opposed to its actual or current selling price.
-
E.
admissionFee
Indicates the monetary charge required for entry or participation in a place, event, or activity.
- 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_69da626cff80819097b530718a7c98b6 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e66fd610f881908fdd22b1f8bd2efc |
completed | April 20, 2026, 6:26 p.m. |
| PD | Predicate disambiguation | batch_69e55b18609481909ab28bc8750a642f |
completed | April 19, 2026, 10:45 p.m. |
Created at: April 11, 2026, 11:39 p.m.