Triple
T23374019
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Caution World Tour |
E593555
|
entity |
| Predicate | hasSetlistContaining |
P33226
|
FINISHED |
| Object | songs from Caution (album) |
—
|
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: songs from Caution (album) | Statement: [Caution World Tour, hasSetlistContaining, songs from Caution (album)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetlistContaining Context triple: [Caution World Tour, hasSetlistContaining, songs from Caution (album)]
-
A.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
-
B.
hasSetlistType
Indicates that an event or performance is associated with a particular type or category of setlist.
-
C.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
D.
featuredInTourSetlistOf
chosen
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
E.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
- 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_69e25d268a50819095f2fd479da8ef3f |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1a3b1d24881909945936cbf00876e |
completed | April 29, 2026, 6:22 a.m. |
| PD | Predicate disambiguation | batch_69f061c7aaa48190a58ce93f87155ffc |
completed | April 28, 2026, 7:29 a.m. |
Created at: April 17, 2026, 5:33 p.m.