Triple
T20816718
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blue Light, Red Light |
E512458
|
entity |
| Predicate | hasBackingEnsemble |
P28442
|
FINISHED |
| Object | big 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: big band | Statement: [Blue Light, Red Light, hasBackingEnsemble, big band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBackingEnsemble Context triple: [Blue Light, Red Light, hasBackingEnsemble, big band]
-
A.
hasBackingBand
chosen
Indicates that an artist or performer is supported musically by a specific band that plays instruments or accompaniment for them.
-
B.
hasBackingVocals
Indicates that one musical performance, track, or part includes supporting vocal contributions accompanying a primary vocal line.
-
C.
hasBackingMusician
Indicates that one entity serves as a supporting or accompanying musician for another entity, typically in a performance or recording context.
-
D.
hasRhythmSection
Indicates that an entity (such as a musical group or piece) includes or is associated with a rhythm section component.
-
E.
hasEnsembles
Indicates that an entity is associated with one or more ensembles, typically as a member, component, or participant.
- 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_69e0b4cd25088190b48ca9700cd24efc |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6c2f3473c81908c43a2ec242b1acd |
completed | April 21, 2026, 12:21 a.m. |
| PD | Predicate disambiguation | batch_69e5c99ca55481908e8d434fa901cfd6 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:41 p.m.