Triple
T8841534
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tomorrowland |
E210398
|
entity |
| Predicate | hasLiveStream |
P80381
|
FINISHED |
| Object | Tomorrowland live stream |
—
|
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 live stream | Statement: [Tomorrowland, hasLiveStream, Tomorrowland live stream]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLiveStream Context triple: [Tomorrowland, hasLiveStream, Tomorrowland live stream]
-
A.
hasLiveBroadcast
Indicates that a live broadcast is currently being transmitted or available for the referenced entity.
-
B.
offersLiveStreaming
chosen
Indicates that one entity provides the capability for real-time (live) streaming of content to another entity or audience.
-
C.
hasStreamingAvailability
Indicates that a media item is available to be streamed through a particular streaming service or platform.
-
D.
broadcastLiveFrom
Indicates that an event or program is being transmitted in real time from a specific location or source.
-
E.
isLiveRecording
Indicates that the recording was captured during a live performance or event rather than produced in a studio or through post-production.
- 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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60876c6c8190b1b490e447e1cf4b |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:48 p.m.