Triple
T36503503
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bad Finger Boogie |
E899400
|
entity |
| Predicate | workingTitleForSongBy |
P85265
|
FINISHED |
| Object | The Beatles |
—
|
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: The Beatles | Statement: [Bad Finger Boogie, workingTitleForSongBy, The Beatles]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: workingTitleForSongBy Context triple: [Bad Finger Boogie, workingTitleForSongBy, The Beatles]
-
A.
isTitleCharacterOfSong
Indicates that a character is mentioned in or constitutes the title of a specific song.
-
B.
hasSongTitle
Indicates that an entity (such as a song or musical work) bears or is associated with a specific song title.
-
C.
titleSongComposer
Indicates that one entity is the composer of the title song associated with another entity (such as a film, show, or album).
-
D.
alternateWorkingTitle
chosen
Indicates that one title serves as an alternative working title for the same work or project as another title.
-
E.
createdForWorkByTitle
Indicates that a work was created specifically for, or commissioned by, a person or entity identified by their title.
- 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_69f76e5b92088190933afda3f7531dd4 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69f7c371931c8190afb1d4dd5157f92c |
completed | May 3, 2026, 9:51 p.m. |
| PD | Predicate disambiguation | batch_69f7c1b91fd88190ab85afd626603769 |
completed | May 3, 2026, 9:44 p.m. |
Created at: May 3, 2026, 4:10 p.m.