Triple
T29218373
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | House of Yes: Live from House of Blues |
E740739
|
entity |
| Predicate | setListSource |
P124129
|
FINISHED |
| Object | Yes back catalogue |
—
|
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: Yes back catalogue | Statement: [House of Yes: Live from House of Blues, setListSource, Yes back catalogue]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: setListSource Context triple: [House of Yes: Live from House of Blues, setListSource, Yes back catalogue]
-
A.
updateSource
Indicates that one entity serves as the origin or provider of information, data, or content used to modify or refresh another entity.
-
B.
hasSetlistSource
chosen
Indicates that a setlist is derived from, documented by, or associated with a particular source or reference.
-
C.
setsNumberOf
Indicates that one entity assigns or defines the numerical quantity or count associated with another entity.
-
D.
setsSelectionPolicyFor
Indicates that one entity defines or configures the selection policy or criteria used by another entity.
-
E.
setsOn
Indicates that one entity places or arranges another entity onto a specified surface, container, or context.
- 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_69f07cba2f808190a2746477d4e8345b |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66430505481909c263d0b8f16309b |
completed | May 2, 2026, 8:53 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 12:14 p.m.