Triple
T31170822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Radiohead live setlists |
E794597
|
entity |
| Predicate | includeDeepCuts |
P137977
|
FINISHED |
| Object | Talk Show Host |
—
|
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: Talk Show Host | Statement: [Radiohead live setlists, includeDeepCuts, Talk Show Host]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: includeDeepCuts Context triple: [Radiohead live setlists, includeDeepCuts, Talk Show Host]
-
A.
includesDeepCuts
chosen
Indicates that the subject contains lesser-known, rare, or non-mainstream items from the object’s collection or repertoire.
-
B.
isDeepCutOn
Indicates that one entity is a relatively obscure, less well-known, or non-mainstream example or item within the context of another entity.
-
C.
includesCrop
Indicates that one entity (such as a field, farm, or agricultural area) contains or has within it a specified crop.
-
D.
includesShorts
Indicates that the subject contains or features short-form content, such as short videos, clips, or brief segments.
-
E.
includedWith
Indicates that one entity is provided or packaged together as part of another entity.
- 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_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
Created at: April 29, 2026, 9:07 p.m.