Triple
T25767290
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chris Cornell concert tours |
E648918
|
entity |
| Predicate | typicalSetlistIncludes |
P33226
|
FINISHED |
| Object | Soundgarden songs |
E25772
|
NE 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: Soundgarden songs | Statement: [Chris Cornell concert tours, typicalSetlistIncludes, Soundgarden songs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSetlistIncludes Context triple: [Chris Cornell concert tours, typicalSetlistIncludes, Soundgarden songs]
-
A.
featuredInTourSetlistOf
chosen
Indicates that an item (such as a song or performance) appears as part of the setlist for a specific tour.
-
B.
repertoireIncludes
Indicates that a collection, such as a performer’s or system’s repertoire, contains or encompasses a particular item, work, or capability.
-
C.
hasSetlistType
Indicates that an event or performance is associated with a particular type or category of setlist.
-
D.
hasSetlistScope
Indicates that a setlist is associated with, or limited to, a particular scope or context (such as a specific event, tour, or performance).
-
E.
hasSetlistSource
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
- F. None of above.
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_69e7ab322db0819092d6a2b3d4572e01 |
completed | April 21, 2026, 4:52 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a10cc1aacf081908a23c0cd6f34678b |
completed | May 22, 2026, 9:35 p.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: April 22, 2026, 5:11 a.m.