Triple
T35563037
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | C. W. (That Thing You Do!) |
E1027686
|
entity |
| Predicate | workAppearedInTheme |
P183798
|
FINISHED |
| Object | one-hit wonder band |
—
|
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: one-hit wonder band | Statement: [C. W. (That Thing You Do!), workAppearedInTheme, one-hit wonder band]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workAppearedInTheme Context triple: [C. W. (That Thing You Do!), workAppearedInTheme, one-hit wonder band]
-
A.
associatedWithAuthorTheme
Indicates a relationship where an author is linked to, or characterized by, a particular theme in their work or thought.
-
B.
composerOfWorkAppearsIn
Indicates that a person is the composer of a musical or artistic work that appears within another work or context.
-
C.
settingOfWorkAppearsIn
Indicates that a particular place, time, or environment serves as the setting within which a given creative work’s events or narrative occur.
-
D.
appearsInWorkByTitle
Indicates that an entity appears in, is featured in, or is contained within a work identified by its title.
-
E.
hasThemeInStory
Indicates that a particular theme is present or plays a significant role within a given story.
- F. None of above. chosen
Provenance (4 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_69f76e020fd8819081cb080e7e203083 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
| PDg | Predicate description generation | batch_69f7a34e80dc8190980d5b7b0b91341d |
completed | May 3, 2026, 7:34 p.m. |
Created at: May 3, 2026, 4:04 p.m.