Triple
T31170794
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radiohead live setlists |
E794597
|
entity |
| Predicate | showcase |
P130339
|
FINISHED |
| Object | Radiohead's musical range |
—
|
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: Radiohead's musical range | Statement: [Radiohead live setlists, showcase, Radiohead's musical range]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showcase Context triple: [Radiohead live setlists, showcase, Radiohead's musical range]
-
A.
helpedShowcase
Indicates that one entity actively assisted in presenting, promoting, or displaying another entity to an audience.
-
B.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
C.
studioShow
Indicates that a show is produced, recorded, or broadcast by a particular studio.
-
D.
exhibitFor
chosen
Indicates a relationship where something is displayed, presented, or shown for the benefit, use, or consideration of a particular audience, purpose, or entity.
-
E.
designedToDemonstrate
Indicates that something was intentionally created or arranged for the purpose of showing, illustrating, or proving a particular concept, feature, or behavior.
- 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_69f224d5b9708190b6ca79ad2fd3a28a |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f69c234d648190a243fb2b107136a9 |
completed | May 3, 2026, 12:51 a.m. |
| PD | Predicate disambiguation | batch_69f69665cd9c819088c388fc82fec42e |
completed | May 3, 2026, 12:27 a.m. |
Created at: April 29, 2026, 9:07 p.m.