Triple
T6415391
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Me First and the Gimme Gimmes |
E127813
|
entity |
| Predicate | typicalSongSource |
P46719
|
FINISHED |
| Object | musicals |
—
|
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: musicals | Statement: [Me First and the Gimme Gimmes, typicalSongSource, musicals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalSongSource Context triple: [Me First and the Gimme Gimmes, typicalSongSource, musicals]
-
A.
sourceSongWork
Indicates that one song work serves as the original source or basis from which another song work is derived, adapted, or referenced.
-
B.
isPopularSongFrom
chosen
Indicates that a song is widely liked, well-known, or frequently played and originates from a particular source, such as an artist, album, or media work.
-
C.
songType
Indicates the specific category or genre that a given song belongs to.
-
D.
hasLyricsSource
Indicates that one entity serves as the source or origin of the lyrics associated with another entity.
-
E.
originalSong
Indicates that one entity is the source or initial version of a song from which another entity (such as a cover, remix, or adaptation) is derived.
- 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_69c0083815208190a9b299b8e0640218 |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c068e6bd3881909b1979de5cdf17fb |
completed | March 22, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69c060f5d4e481909d1366190607b586 |
completed | March 22, 2026, 9:36 p.m. |
Created at: March 22, 2026, 4:42 p.m.