Triple
T31159578
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Eraser live band |
E794301
|
entity |
| Predicate | basedOnStudioWorkOf |
P15523
|
FINISHED |
| Object | Thom Yorke |
—
|
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: Thom Yorke | Statement: [The Eraser live band, basedOnStudioWorkOf, Thom Yorke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnStudioWorkOf Context triple: [The Eraser live band, basedOnStudioWorkOf, Thom Yorke]
-
A.
adaptedWorkOf
chosen
Indicates that one work is derived from, based on, or reinterprets the content of another pre-existing work.
-
B.
producedForStudio
Indicates that a work (such as a film, show, or recording) was created under contract for, and on behalf of, a particular studio.
-
C.
workProducedByStudio
Indicates that a work (such as a film, show, or other production) was created or produced by a particular studio.
-
D.
basedOnFilmDirector
Indicates that something is derived from, adapted from, or otherwise conceptually grounded in the work or role of a particular film director.
-
E.
basedOnWorkForFilm
Indicates that a film is created or derived from a specific underlying work (such as a book, play, or earlier screenplay).
- 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_69f224d504908190b01278dcb7fc3fa7 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69fdd5fba5048190b7d430ae2054a1fd |
completed | May 8, 2026, 12:24 p.m. |
| PD | Predicate disambiguation | batch_69fdd35f76f88190a1854ea27132f9c7 |
completed | May 8, 2026, 12:13 p.m. |
Created at: April 29, 2026, 9:07 p.m.