Triple
T29957307
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Library (Tomorrowland stage) |
E760935
|
entity |
| Predicate | targetGenreFocus |
P82410
|
FINISHED |
| Object | club-oriented electronic music |
—
|
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: club-oriented electronic music | Statement: [The Library (Tomorrowland stage), targetGenreFocus, club-oriented electronic music]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: targetGenreFocus Context triple: [The Library (Tomorrowland stage), targetGenreFocus, club-oriented electronic music]
-
A.
targetGenre
chosen
Indicates the genre that something is specifically aimed at, categorized under, or intended to belong to.
-
B.
networkGenreFocus
Indicates that a network primarily centers its content or programming around a particular genre.
-
C.
genreWithin
Indicates that one genre is a subgenre or more specific category contained within another, broader genre.
-
D.
favoriteGenre
Indicates that one entity’s preferred or most liked genre, among several possible genres, is the other entity.
-
E.
commonGenre
Indicates that two entities share at least one genre in common.
- 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_69fd2a215d6c8190a1a428ccaee603f1 |
completed | May 8, 2026, 12:11 a.m. |
| PD | Predicate disambiguation | batch_69fd28ef19688190bb8370f2812a43e7 |
completed | May 8, 2026, 12:06 a.m. |
Created at: April 29, 2026, 6:27 p.m.