Triple
T23522711
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 2015 Fall Tour |
E574550
|
entity |
| Predicate | setlistIncludesSongsBy |
P88838
|
FINISHED |
| Object | Grateful Dead |
—
|
NE NERFINISHED |
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: Grateful Dead | Statement: [2015 Fall Tour, setlistIncludesSongsBy, Grateful Dead]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setlistIncludesSongsBy Context triple: [2015 Fall Tour, setlistIncludesSongsBy, Grateful Dead]
-
A.
includesSongsFrom
chosen
Indicates that one collection, playlist, or set contains one or more songs that originate from another specified source or group.
-
B.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
C.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
-
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.
hasSetlistType
Indicates that an event or performance is associated with a particular type or category of setlist.
- 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_69e245bb3dcc8190ba9a2b35972b58d0 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1ac70b7888190b4abc4f78bdf539c |
completed | April 29, 2026, 7 a.m. |
| PD | Predicate disambiguation | batch_69f1189d75b48190a1c01928a993c9fb |
completed | April 28, 2026, 8:29 p.m. |
Created at: April 17, 2026, 6:08 p.m.