Triple
T5029009
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Apple Worldwide Developers Conference 2011 |
E113248
|
entity |
| Predicate | ticketSoldOutTime |
P3999
|
FINISHED |
| Object | within hours |
—
|
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: within hours | Statement: [Apple Worldwide Developers Conference 2011, ticketSoldOutTime, within hours]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ticketSoldOutTime Context triple: [Apple Worldwide Developers Conference 2011, ticketSoldOutTime, within hours]
-
A.
ticketDemand
Indicates that there is a level of desire or need among potential buyers for tickets to an event, service, or offering.
-
B.
sellsTicketsUnder
Indicates that one entity sells tickets at a price lower than or under the pricing of another entity.
-
C.
closingAuctionTimeLocal
Indicates the local-time moment at which an auction or bidding process is scheduled to end.
-
D.
firstEditionSoldOutTime
chosen
Indicates the point in time at which the first edition of an item became completely sold out.
-
E.
presentedAtTime
Indicates that an event, action, or item was presented or occurred at a specific point in time.
- 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_69bd443775e48190a646ffbfc4334723 |
completed | March 20, 2026, 12:57 p.m. |
| NER | Named-entity recognition | batch_69bd738f2cc88190a03eebf19e407411 |
completed | March 20, 2026, 4:19 p.m. |
| PD | Predicate disambiguation | batch_69bd71509e9c8190a60c1d8d04936a12 |
completed | March 20, 2026, 4:09 p.m. |
Created at: March 20, 2026, 1:36 p.m.