Triple
T36514223
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Looks Like Rain |
E899992
|
entity |
| Predicate | hasSetlistRole |
P148390
|
FINISHED |
| Object | often played as a ballad in second sets |
—
|
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: often played as a ballad in second sets | Statement: [Looks Like Rain, hasSetlistRole, often played as a ballad in second sets]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSetlistRole Context triple: [Looks Like Rain, hasSetlistRole, often played as a ballad in second sets]
-
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.
setlistRole
chosen
Indicates the specific function or position an entity holds within a setlist, such as performer, opener, or headliner.
-
C.
hasSetlistType
Indicates that an event or performance is associated with a particular type or category of setlist.
-
D.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
E.
hasSetlistSpanning
Indicates that a setlist covers or includes items from a specified range, period, or collection.
- 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_69f76e5dada881909da2d34bc7a9202a |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a0058c341ac8190825067dc25158839 |
completed | May 10, 2026, 10:06 a.m. |
| PD | Predicate disambiguation | batch_6a005857249c81908b27587b84d84dbb |
completed | May 10, 2026, 10:05 a.m. |
Created at: May 3, 2026, 4:10 p.m.