Triple
T30468072
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soulfire Tour |
E775205
|
entity |
| Predicate | performedRepertoireType |
P84416
|
FINISHED |
| Object | solo material by Steven Van Zandt |
—
|
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: solo material by Steven Van Zandt | Statement: [Soulfire Tour, performedRepertoireType, solo material by Steven Van Zandt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: performedRepertoireType Context triple: [Soulfire Tour, performedRepertoireType, solo material by Steven Van Zandt]
-
A.
featuresRepertoireType
chosen
Indicates that something includes or is associated with a particular type or category of repertoire.
-
B.
typeOfPerformances
Indicates the kinds or categories of performances associated with or offered by an entity.
-
C.
performsSongType
Indicates that an entity (such as a performer) carries out or presents a specific type or category of song.
-
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.
repertorySystem
Indicates a relationship where an entity is organized, managed, or presented within a structured repertory or catalog-like system.
- 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_69f2249622a48190b1fae2e3e4ee958a |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fd5d48855c8190bd93070b6a00d8b5 |
completed | May 8, 2026, 3:49 a.m. |
| PD | Predicate disambiguation | batch_69fd5c9aabb88190912800d90184a89d |
completed | May 8, 2026, 3:46 a.m. |
Created at: April 29, 2026, 8:11 p.m.