Triple
T29720433
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UK 2015 Face the Music Tour (live releases) |
E752041
|
entity |
| Predicate | subjectTourArtist |
P88801
|
FINISHED |
| Object | Electric Light Orchestra |
—
|
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: Electric Light Orchestra | Statement: [UK 2015 Face the Music Tour (live releases), subjectTourArtist, Electric Light Orchestra]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: subjectTourArtist Context triple: [UK 2015 Face the Music Tour (live releases), subjectTourArtist, Electric Light Orchestra]
-
A.
touringArtist
Indicates that an artist is currently traveling to perform or exhibit their work in multiple locations.
-
B.
tourForArtist
chosen
Indicates a relationship where a tour is organized for, associated with, or performed by a specific artist.
-
C.
selectedArtist
Indicates that a particular artist has been chosen or designated from a set of possible artists.
-
D.
capturesArtistAt
Indicates a relationship where an entity records or depicts an artist at a particular moment, event, or context.
-
E.
invitedArtist
Indicates that one entity has extended an invitation to another entity in the role of an artist.
- 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 28, 2026, 7:36 p.m.