Triple
T29958213
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Full Madness Pass |
E760966
|
entity |
| Predicate | canBePurchasedVia |
P51662
|
FINISHED |
| Object | Tomorrowland official website |
—
|
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: Tomorrowland official website | Statement: [Full Madness Pass, canBePurchasedVia, Tomorrowland official website]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canBePurchasedVia Context triple: [Full Madness Pass, canBePurchasedVia, Tomorrowland official website]
-
A.
canBePurchasedWith
Indicates that one entity is able to be bought or acquired using another entity as the form of payment.
-
B.
canBePurchased
Indicates that one entity is available to be bought or acquired in exchange for payment by another entity.
-
C.
purchasedIn
Indicates that a purchasing event occurred within or at a specific location or context (such as a store, city, or country).
-
D.
buyIn
Indicates that one party purchases or acquires an ownership stake, participation, or commitment in something initiated or owned by another party.
-
E.
isSoldIn
chosen
Indicates that a product or item is available for purchase within a specified location, market, or sales channel.
- 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_69f22466327481908ba6db916837bece |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fd4d1854988190be093b103a681798 |
completed | May 8, 2026, 2:40 a.m. |
| PD | Predicate disambiguation | batch_69fd4c8d1a188190897c24527337814a |
completed | May 8, 2026, 2:38 a.m. |
Created at: April 29, 2026, 6:28 p.m.