Triple
T36539049
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nobody’s Side |
E900665
|
entity |
| Predicate | isPopularAuditionPiece |
P185825
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nobody’s Side, isPopularAuditionPiece, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isPopularAuditionPiece Context triple: [Nobody’s Side, isPopularAuditionPiece, true]
-
A.
isPopularSong
Indicates that a song is widely liked, well-known, or frequently listened to by many people.
-
B.
isPopularSongFor
Indicates that a song is widely liked, well-known, or frequently chosen by a particular audience, group, or context.
-
C.
isPopularSongOf
Indicates that a song is widely liked, well-known, or frequently enjoyed in relation to a particular entity (such as an artist, album, or context).
-
D.
isPopularMusicStandard
Indicates that a piece of music is widely recognized, frequently performed, and accepted as part of the standard popular music repertoire.
-
E.
isPopularSongFrom
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.
- 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_69f76e5fbb388190b70c4c15573c8143 |
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. |
| PDg | Predicate description generation | batch_69f7c3705b5c81908c84004543a71c07 |
completed | May 3, 2026, 9:51 p.m. |
Created at: May 3, 2026, 4:11 p.m.