Triple
T22708875
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Death By Stereo |
E561536
|
entity |
| Predicate | mainPerformerLineup |
P149405
|
FINISHED |
| Object | band |
—
|
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: band | Statement: [Death By Stereo, mainPerformerLineup, band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainPerformerLineup Context triple: [Death By Stereo, mainPerformerLineup, band]
-
A.
originalPerformerLineup
Indicates that the subject is associated with the initial or first group of performers who originally performed an event, work, or production.
-
B.
typicalPerformers
Indicates the entities that most commonly or characteristically perform a given action or role.
-
C.
partOfBandLineup
Indicates that an entity is a member of, or included in, the lineup of a particular band.
-
D.
mainPerformerMemberOf
Indicates that the primary performer in an event or work is a member of a specified group, band, ensemble, or organization.
-
E.
associatedBandLineup
Indicates that there is a specific band lineup (i.e., configuration of band members) that is linked or connected to the given entity.
- F. None of above. chosen
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_69e2454f1348819088d83f420925a5c1 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f178d11d4081909981872698b6c45e |
completed | April 29, 2026, 3:19 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:17 p.m.