Triple
T30418039
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Rising Tour |
E773812
|
entity |
| Predicate | featuredBandMember |
P45823
|
FINISHED |
| Object | Steven Van Zandt |
—
|
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: Steven Van Zandt | Statement: [The Rising Tour, featuredBandMember, Steven Van Zandt]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredBandMember Context triple: [The Rising Tour, featuredBandMember, Steven Van Zandt]
-
A.
touringBandMember
Indicates that a person is a member of a band specifically in the context of its touring or live performance lineup.
-
B.
houseBandMember
Indicates that a person is a member of a house band, typically performing regularly as part of that resident musical group.
-
C.
contributingBandMember
Indicates that an individual is a member of a band who contributes to its music, performance, or creative output.
-
D.
featuresBandMembers
chosen
Indicates that something includes or presents specific band members as part of its content or composition.
-
E.
featuresFormerBandMemberOf
Indicates that the subject entity includes, highlights, or presents an individual who was previously a member of the referenced band.
- 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_69f22491ba248190b9a4776ca8e42d02 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fff9b126b4819085a4cf8791d388d1 |
completed | May 10, 2026, 3:21 a.m. |
| PD | Predicate disambiguation | batch_69fff8f913a881908d3b7e490d92631f |
completed | May 10, 2026, 3:18 a.m. |
Created at: April 29, 2026, 8:05 p.m.