Triple
T23552422
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yield Tour |
E578087
|
entity |
| Predicate | setlistCharacteristic |
P152768
|
FINISHED |
| Object | frequent changes between shows |
—
|
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: frequent changes between shows | Statement: [Yield Tour, setlistCharacteristic, frequent changes between shows]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setlistCharacteristic Context triple: [Yield Tour, setlistCharacteristic, frequent changes between shows]
-
A.
setlistRole
Indicates the specific function or position an entity holds within a setlist, such as performer, opener, or headliner.
-
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
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
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. chosen
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_69e245fa93448190919cb04534560542 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f1aed096b08190a8a755eaa7663fba |
completed | April 29, 2026, 7:10 a.m. |
| PD | Predicate disambiguation | batch_69f118afabd88190bd88f49597d120e8 |
completed | April 28, 2026, 8:29 p.m. |
| PDg | Predicate description generation | batch_69f121cc494081908c987adfcde89b0e |
completed | April 28, 2026, 9:08 p.m. |
Created at: April 17, 2026, 6:11 p.m.