Triple
T29221052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Along for the Ride Tour |
E740804
|
entity |
| Predicate | setlistType |
P106960
|
FINISHED |
| Object | career-spanning |
—
|
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: career-spanning | Statement: [Along for the Ride Tour, setlistType, career-spanning]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setlistType Context triple: [Along for the Ride Tour, setlistType, career-spanning]
-
A.
hasSetlistType
chosen
Indicates that an event or performance is associated with a particular type or category of setlist.
-
B.
setlistCharacteristic
Indicates that a particular property or feature characterizes or describes a musical setlist.
-
C.
setlistRole
Indicates the specific function or position an entity holds within a setlist, such as performer, opener, or headliner.
-
D.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
E.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f664329c8c8190abdb1a68f7362c98 |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:15 p.m.