Triple
T30418030
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rising Tour |
E773812
|
entity |
| Predicate | typicalSetlistIncludedSong |
P33226
|
FINISHED |
| Object | The Rising |
E40120
|
NE 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: The Rising | Statement: [The Rising Tour, typicalSetlistIncludedSong, The Rising]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSetlistIncludedSong Context triple: [The Rising Tour, typicalSetlistIncludedSong, The Rising]
-
A.
typicalSetlistStatus
Indicates the usual or expected status of an item within a standard or commonly performed setlist.
-
B.
featuredInTourSetlistOf
chosen
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
C.
hasSetlistSpanning
Indicates that a setlist covers or includes items from a specified range, period, or collection.
-
D.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
E.
setlistCharacteristic
Indicates that a particular property or feature characterizes or describes a musical setlist.
- F. None of above.
Provenance (4 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2798af7460819085eb85d40e55d154 |
completed | June 9, 2026, 4:38 a.m. |
| PD | Predicate disambiguation | batch_6a0379e2fac0819089b522db3260028c |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 8:05 p.m.