Triple
T33364656
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stairsteps – 2nd Resurrection |
E854316
|
entity |
| Predicate | mainPerformerVocalGroup |
P138748
|
FINISHED |
| Object | Five Stairsteps |
—
|
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: Five Stairsteps | Statement: [Stairsteps – 2nd Resurrection, mainPerformerVocalGroup, Five Stairsteps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformerVocalGroup Context triple: [Stairsteps – 2nd Resurrection, mainPerformerVocalGroup, Five Stairsteps]
-
A.
vocalGroupOnNotableRecording
chosen
Indicates that a vocal group performed on or contributed vocals to a notable audio recording.
-
B.
vocalGroupMemberOnRecording
Indicates that a person is a member of a vocal group that performs on a particular recording.
-
C.
vocalGroupPosition
Indicates the role or placement an entity holds within a vocal group, such as their part, rank, or position in the ensemble.
-
D.
performerEnsemble
Indicates a relationship where an individual performer is associated with, or is a member of, a musical or artistic ensemble.
-
E.
singsWith
Indicates that two or more entities perform singing together, jointly participating in a vocal musical activity.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f760a35b988190904e6267553ad2fe |
completed | May 3, 2026, 2:50 p.m. |
| PD | Predicate disambiguation | batch_69f75eb3d6f081908c933474eb359e3d |
completed | May 3, 2026, 2:41 p.m. |
Created at: May 1, 2026, 1:34 a.m.